[
https://issues.apache.org/jira/browse/IGNITE-28851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-28851:
------------------------------------
Description: The main goal of this ticket is to provide a mechanism that
guarantees the same serialization order of message fields across nodes running
different Ignite versions, both while a Rolling Upgrade is in progress and
after it has been completed. (was: The main goal of this ticket is to provide
a mechanism that guarantees the same serialization order of message fields
across nodes running different Ignite versions, both while a Rolling Upgrade is
in progress and after it has been completed.
To achieve symmetric serialization behavior across nodes, the serialization
process should use the node's local feature set and the active cluster feature
set.)
> Embed Ignite Features to Serialization Mechanism for transport between Ignite
> nodes
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-28851
> URL: https://issues.apache.org/jira/browse/IGNITE-28851
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: IEP-132, ise
> Fix For: 2.19
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The main goal of this ticket is to provide a mechanism that guarantees the
> same serialization order of message fields across nodes running different
> Ignite versions, both while a Rolling Upgrade is in progress and after it has
> been completed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
