[
https://issues.apache.org/jira/browse/IOTDB-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617081#comment-17617081
]
yang caiyin commented on IOTDB-3936:
------------------------------------
To better solve this problem, besides executeStatementV2. We should also add
fetchResultV2、executeRawDataQuery and executeLastDataQuery to replace the
former method for a faster query without queryDataset.
> Add an interface in IClientRPCService to directly use TsBlock instead of
> TSQueryDataSet
> ---------------------------------------------------------------------------------------
>
> Key: IOTDB-3936
> URL: https://issues.apache.org/jira/browse/IOTDB-3936
> Project: Apache IoTDB
> Issue Type: Improvement
> Reporter: Yuan Tian
> Assignee: yang caiyin
> Priority: Major
>
> Currently, we convert TsBlock to TSQueryDataSet to be compatible with
> previous executeStatement() interface in IClientRPCService and in this way we
> won't need to change all other language clients like go, C/C++ and python etc.
> However, we can add a new interface like executeStatementV2 to directly
> return serialized form of TsBlock to client and then do the deserialization
> things in the client end. In this way, we can improve the query performance
> if the result TsBlock is received from remote node. Because in such case,
> what we received is already serialized TsBlock(in ByteBuffer form), we can
> directly return that to client which will saving one deserializing TsBlock
> and one serialzie to TSQueryDataSet.
> We alse need to change the java client: jdbc and session to adapt to read
> from TsBlock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
