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

Posted to issues@ignite.apache.org by "Nikita Amelchev (Jira)" <ji...@apache.org> on 2024/11/29 18:57:00 UTC

[jira] [Updated] (IGNITE-20913) Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve

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

Nikita Amelchev updated IGNITE-20913:
-------------------------------------
    Fix Version/s: 2.18
                       (was: 2.17)

> Previous value, version, their combination or parts should be written as a part of the DataEntry to allow CacheVersionConflictResolver use them on resolve
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-20913
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20913
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>              Labels: ise
>             Fix For: 2.18
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Just allowing CacheVersionConflictResolver to resolve -more- complex cases.
> Main goal is to allow any changes from other cluster when both clusters are synchronized (have the same value/version).



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