[jira] [Commented] (IGNITE-21228) Data not available thtough JDBC after inserting using KV for a while
[ https://issues.apache.org/jira/browse/IGNITE-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817955#comment-17817955 ] Maksim Zhuravkov commented on IGNITE-21228: --- 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)
[jira] [Commented] (IGNITE-21228) Data not available thtough JDBC after inserting using KV for a while
[ https://issues.apache.org/jira/browse/IGNITE-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814781#comment-17814781 ] Maksim Zhuravkov commented on IGNITE-21228: --- [~jooger] If data is inserted via server API, then it looks like all client APIs are affected. > 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)
[jira] [Commented] (IGNITE-21228) Data not available thtough JDBC after inserting using KV for a while
[ https://issues.apache.org/jira/browse/IGNITE-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814766#comment-17814766 ] Maksim Zhuravkov commented on IGNITE-21228: --- [~jooger] other APIs does not suffer from this issue. > 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)
[jira] [Commented] (IGNITE-21228) Data not available thtough JDBC after inserting using KV for a while
[ https://issues.apache.org/jira/browse/IGNITE-21228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805081#comment-17805081 ] Yury Gerzhedovich commented on IGNITE-21228: [~Berkov] could you confirm that the rows available through java API in the same time? > 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 > > # 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)
