[
https://issues.apache.org/jira/browse/IOTDB-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196948#comment-17196948
]
WangChao commented on IOTDB-883:
--------------------------------
If the user care the insertRecord result and they will use
insertStringRecordToBuffer, why not use insertRecords?
We should provide a asynchronous insertStringRecordToBuffer which could
implement the callback function to notify the result to the user.
Maybe client need to maintain a map <recordId, record>, and then retry the
failed record when received the result. So the interface will be
insertStringRecordToBuffer(recordId, record). And we need to callback user to
tell the results and related recordId?
> Buffered insertion interface
> ----------------------------
>
> Key: IOTDB-883
> URL: https://issues.apache.org/jira/browse/IOTDB-883
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Client/Java
> Reporter: Jialin Qiao
> Assignee: Haimei Guo
> Priority: Minor
>
> InsertRecords is more efficient than insertRecord. If the user could bare
> some insertion latency, we could cache the records in the client-side and
> sent a batch of records periodically to the server.
> The interface may look like insertRecord(parameters, long latency)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
