[IGNITE-19241] Java thin 3.0: propagate table schema updates to client on write-only operations

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 3.0.0-beta2
• Component/s: thin client
• Labels: ignite-3

Language

Java

• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 06/Apr/23 09:08
• Updated: 02/May/23 11:31
• Resolved: 25/Apr/23 09:38

Description

Currently, Java client receives table schema updates when write-read requests are performed. For example, client performs TUPLE_GET request, sends key tuple using old schema version, receives result tuple with the latest schema version, and retrieves the latest schema.

However, some requests are "write-only": client sends a tuple, but does not receive one back, like TUPLE_UPSERT. No schema updates are performed in this case.

To fix this, include the latest schema version into all write-only operation responses:

• TUPLE_UPSERT
• TUPLE_UPSERT_ALL
• TUPLE_INSERT
• TUPLE_INSERT_ALL
• TUPLE_REPLACE
• TUPLE_REPLACE_EXACT
• TUPLE_DELETE
• TUPLE_DELETE_ALL
• TUPLE_DELETE_EXACT
• TUPLE_DELETE_ALL_EXACT
• TUPLE_CONTAINS_KEY

Client will compare this version to the known one and perform a background update, if necessary.

Issue Links

• is cloned by: IGNITE-19243 C++ 3.0: propagate table schema updates to client on write-only operations
• is cloned by: IGNITE-19242 .NET: Thin 3.0: propagate table schema updates to client on write-only operations
• is superceded by: IGNITE-19397 Thin 3.0: Return an error to client when outdated schema is used
• relates to: IGNITE-19354 Java thin 3.0: Same schema version is retrieved multiple times in concurrent scenarios
• links to: GitHub Pull Request #1975
• links to: IGNITE-19241 Java client: propagate schema updates to client on write-only operations DRAFT by ptupitsyn · Pull Request #1975 · apache/ignite-3