You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2021/10/18 16:18:00 UTC

[jira] [Updated] (IGNITE-15492) Check schema availability on local node

     [ https://issues.apache.org/jira/browse/IGNITE-15492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lapin updated IGNITE-15492:
-------------------------------------
        Parent:     (was: IGNITE-14209)
    Issue Type: Improvement  (was: Sub-task)

> Check schema availability on local node
> ---------------------------------------
>
>                 Key: IGNITE-15492
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15492
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vyacheslav Koptilin
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently, we do not check that a schema that is needed for deserialization returned tuple (for example, the end-user calls tableKvView.get(key) method) is available on the local node that performs table operation.
> Need to implement a synchronization mechanism that allows overcoming an issue related to the deserialization of tuples. Looks like it is an actual issue regardless of rebalancing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)