Add support for STRING type - #99
Open
q977734161 wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
HTHou
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
I want to use STRING type data, but the current SINK does not support it.
Why Use STRING type
IoTDB version 1.3.X has added support for the STRING type. The difference between STRING and TEXT types is that STRING type carries more statistical information, which can be used to optimize value-filtering queries. TEXT type is more suitable for storing long strings.
Key changed/added classes (or packages if there are too many classes) in this PR
DefaultIoTSerializationSchema.java -> serialize(Map<String, String> tuple)
IoTDBSink.java -> convertText(String device, List measurements, List values)