[
https://issues.apache.org/jira/browse/IGNITE-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817955#comment-17817955
]
Maksim Zhuravkov edited comment on IGNITE-21228 at 2/16/24 12:49 PM:
---------------------------------------------------------------------
This issue was caused by introduction of a separate `HybridTimestampTracker`
for a client module in https://issues.apache.org/jira/browse/IGNITE-19889
(There is TODO that states there are additional changes be done as part of
IGNITE-20232)
was (Author: JIRAUSER298618):
This issue was caused by introduction of a separate `HybridTimestampTracker`
for a client module in https://issues.apache.org/jira/browse/IGNITE-19889 (see
TODO: IGNITE-20232)
> Data not available thtough JDBC after inserting using KV for a while
> --------------------------------------------------------------------
>
> Key: IGNITE-21228
> URL: https://issues.apache.org/jira/browse/IGNITE-21228
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 3.0
> Reporter: Alexander Belyak
> Priority: Major
> Labels: ignite-3
>
> # Create table using java API
> # Insert 100 rows using sync KV java API
> # Connect using JDBC and try to select inserted data
> Expected result: all rows available
> Actual result: no rows available for a few hundreds of milliseconds
> (700-1000ms on my laptop).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
