Roman Puchkovskiy created IGNITE-19796:
------------------------------------------
Summary: Wait on schema update future without waiting for
metastore watches of the update
Key: IGNITE-19796
URL: https://issues.apache.org/jira/browse/IGNITE-19796
Project: Ignite
Issue Type: Improvement
Reporter: Roman Puchkovskiy
Fix For: 3.0.0-beta2
In IGNITE-19209, the wait mechanism on a future of a schema update works like
this:
# Write the update to the metastore using multiInvoke
# Wait for the corresponding entry to be consumed and processed on the same
node
# Take activation timestamp from the internal structures of CatalogService
(filled on step 2) and use it to calculate the target wait timestamp
The wait on step 2 seems excessive as the call on step 1 can return the
revision timestamp, which can be used to recover the activation timestamp. A
necessity to do step 2 means we depend on the MetaStorage communication from
the leader to the current node, which might cause more wait for the user than
required.
IGNITE-19795 implements a mechanism to make step 2 obsolete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
