Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
3.0.0-beta1
Description
Currently, .NET 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.
Attachments
Issue Links
- is a clone of
-
IGNITE-19241 Java thin 3.0: propagate table schema updates to client on write-only operations
-
- Resolved
-
- is superceded by
-
IGNITE-19397 Thin 3.0: Return an error to client when outdated schema is used
-
- Resolved
-
- relates to
-
IGNITE-19355 .NET: Thin 3.0: Same schema version is retrieved multiple times in concurrent scenarios
-
- Resolved
-
- links to