IGNITE-24055 Sql. Update the observation timestamp only after processing DDL statements #5032
+150
−150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/IGNITE-24055
CatalogUtils
.clusterWideEnsuredActivationTsSafeForRoReads
. Otherwise these changes seem useless. The description of IGNITE-20378 looks outdated because it is about different clients, but at the moment the concept has changed and we guarantee the visibility of changes only within one client instance.testClientPropagatesLatestKnownHybridTimestamp
(fromObservableTimestampPropagationTest
) has been trimmed since the observable time is now updated inside the query execution, and an additional testddlExecutionUpdatesObservableTime
(ExecutionServiceImplTest
) has been added to verify this.