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

Posted to issues@ignite.apache.org by "Valentin Kulichenko (Jira)" <ji...@apache.org> on 2022/01/17 00:19:00 UTC

[jira] [Updated] (IGNITE-15948) Implement class structure change handling

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

Valentin Kulichenko updated IGNITE-15948:
-----------------------------------------
    Fix Version/s: 3.0.0-alpha5
                       (was: 3.0.0-alpha4)

> Implement class structure change handling
> -----------------------------------------
>
>                 Key: IGNITE-15948
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15948
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Semyon Danilov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha5
>
>
> User objects may change their class definition (e.g. class can lose its final modifier, can become private, or in other means inaccessible). Ignite should make the best effort at merging different versions of descriptors and parsing objects.
> See https://github.com/gridgain/gridgain-9-ce/blob/iep-67/modules/network/README.md#handling-class-structure-changes



--
This message was sent by Atlassian Jira
(v8.20.1#820001)