[jira] [Commented] (IGNITE-17864) Optimize scan(HybridTimestamp.MAX_VALUE) and read(HybridTimestamp.MAX_VALUE)
[ https://issues.apache.org/jira/browse/IGNITE-17864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624615#comment-17624615 ] Semyon Danilov commented on IGNITE-17864: - Just a notification: had to push it into the beta1 branch, because it's needed for https://issues.apache.org/jira/browse/IGNITE-17968 > Optimize scan(HybridTimestamp.MAX_VALUE) and read(HybridTimestamp.MAX_VALUE) > > > Key: IGNITE-17864 > URL: https://issues.apache.org/jira/browse/IGNITE-17864 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 40m > Remaining Estimate: 0h > > Please check https://issues.apache.org/jira/browse/IGNITE-17856 for more > details about scan(UUID txId) and read(RowId rowId, UUID txId) removal. > Within given ticket it's expected that timestamp based scans and reads will > be optimized in order to perform HybridTimestamp.MAX_VALUE bouned operations > in a most efficient way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17864) Optimize scan(HybridTimestamp.MAX_VALUE) and read(HybridTimestamp.MAX_VALUE)
[ https://issues.apache.org/jira/browse/IGNITE-17864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618931#comment-17618931 ] Roman Puchkovskiy commented on IGNITE-17864: Thanks! > Optimize scan(HybridTimestamp.MAX_VALUE) and read(HybridTimestamp.MAX_VALUE) > > > Key: IGNITE-17864 > URL: https://issues.apache.org/jira/browse/IGNITE-17864 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 40m > Remaining Estimate: 0h > > Please check https://issues.apache.org/jira/browse/IGNITE-17856 for more > details about scan(UUID txId) and read(RowId rowId, UUID txId) removal. > Within given ticket it's expected that timestamp based scans and reads will > be optimized in order to perform HybridTimestamp.MAX_VALUE bouned operations > in a most efficient way. -- This message was sent by Atlassian Jira (v8.20.10#820010)
