[
https://issues.apache.org/jira/browse/IGNITE-24053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916125#comment-17916125
]
Pavel Tupitsyn commented on IGNITE-24053:
-----------------------------------------
Cherry-picked to ignite-3.0:
[201153fce649fb2cb635d2b7c8dfdae4a8317bbf|https://github.com/apache/ignite-3/commit/201153fce649fb2cb635d2b7c8dfdae4a8317bbf]
> Attach observation timestamp for JDBC client requests
> -----------------------------------------------------
>
> Key: IGNITE-24053
> URL: https://issues.apache.org/jira/browse/IGNITE-24053
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3, important
> Fix For: 3.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> h3. Motivation
> Among the JDBC requests, we can have read requests that required an
> observation timestamp to calculate the read timestamp correctly.
> It is already done for SQL requests ({{ClientSqlExecuteRequest,
> ClientSqlExecuteBatchRequest, ClientSqlExecuteScriptRequest}}) and have to
> do the same for the JDBC.
> h3. Definition of done
> * JdbcQueryEventHandlerImpl#timestampTracker oughе to disappear
> * The observation timestamp should be tracked only on the client side
> (dedicated for any client)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
