[IGNITE-19796] Wait on schema update future without waiting for metastore watches of the update

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.0
• Labels: ignite-3 tech-debt
• Assignee: Unassigned
• Reporter: Roman Puchkovskiy
• Created: 21/Jun/23 14:06
• Updated: 04/Sep/24 16:10

Description

In IGNITE-19209, the wait mechanism on a future of a schema update works like this:

1. Write the update to the metastore using multiInvoke
2. Wait for the corresponding entry to be consumed and processed on the same node
3. 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.

Issue Links

• is related to: IGNITE-19795 Allow MetaStorage return the created revision timestamp from multiInvoke
• is related to: IGNITE-19209 Implement installing table schema updates