[IOTDB-1515]Fix binary convertion in LastQueryExecutor#3605
[IOTDB-1515]Fix binary convertion in LastQueryExecutor#3605ericpai wants to merge 1 commit intoapache:masterfrom
Conversation
|
Hi, currently we can only insert any bytes with Binary by insertTablet interface, right? InsertRecord interface only support insert String record. If we consider to support any bytes, some modification of insertRecord is needed I think… |
575c95b to
01cc43d
Compare
@HTHou Yes, InsertRecord treats the input Maybe we can indicate that only valid UTF-8 String supported in TEXT type in However this PR is the superset of UTF-8 string support(I can add another test case for valid utf8 bytes). Do you think it should be merged? |
|
Hi, the data type of Binary is TEXT, so it's before only store UTF-8 String. If we want to store bytes, we could import another data type called BINARY. This could be discussed in the mail list :) |
It makes sense! Currently I will use base64 encoding as a workaround solution to store arbitrary bytes. This PR and JIRA will be closed. |
|
@ericpai , we indeed need a new binary (better to be called as Blob) data type, which stores bytes and has no statistics like sum etc (first value and last value are also not needed by default).. Then, current binary can be renamed as Clob or Text directly (but we need to consider compatibility) |
Please see JIRA https://issues.apache.org/jira/browse/IOTDB-1515 .
Here are another two questions. Any guidance or discussion is welcomed :).
Binarytype designed for? Any bytes or only valid UTF-8 strings?AbstractIoTDBJDBCResultSet.getBytesis needed. As we cannot restore orignal binary data from a malformed UTF-8 string.If this PR is accepted. I think it should be cherry-picked to release branches.