Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Motivation
client1.sql(CREATE TABLE t1);
client.beginRO()
client.sql(SELECT * from t1); // Given request should see t1.
...
However it won't be true by default because we may step back for idle safe time propagation period that might be greater than delay duration in metadata sync logic.
Definition of Done
- Both clients and embedded nodes should have an ability to see same-actor schema adjustments though RO requests.
Implementation Notes
Seems that it's required to adjust observable timestamp within DDL operations or we may consider setting DD greater than idle safe time propagation period.
Attachments
Issue Links
- blocks
-
IGNITE-22516 Shorten waiting out clock skew on DDL execution
- Reopened
- is blocked by
-
IGNITE-23806 Investigate the possibility of generalizing the logic for working with maxObservableTimestamp.
- Open
- relates to
-
IGNITE-20668 Increase wait after a DDL to account for idle safe-time propagation period
- Resolved
-
IGNITE-20699 Decrease idle safe time propagation period in tests
- Resolved
-
IGNITE-22500 Remove unnecessary waits when creating an index
- Resolved
- links to