You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2023/04/06 09:16:00 UTC

[jira] [Created] (IGNITE-19242) .NET: Thin 3.0: propagate table schema updates to client on write-only operations

Pavel Tupitsyn created IGNITE-19242:
---------------------------------------

             Summary: .NET: Thin 3.0: propagate table schema updates to client on write-only operations
                 Key: IGNITE-19242
                 URL: https://issues.apache.org/jira/browse/IGNITE-19242
             Project: Ignite
          Issue Type: Improvement
          Components: thin client
    Affects Versions: 3.0.0-beta1
            Reporter: Pavel Tupitsyn
            Assignee: Pavel Tupitsyn
             Fix For: 3.0.0-beta2


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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)