[jira] [Commented] (IGNITE-21285) Data entries looped in CDC if ExpirePolicy is set

["Nikita Amelchev (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819177#comment-17819177 ] 

Nikita Amelchev commented on IGNITE-21285:
------------------------------------------

Merged into the master.

[~timonin.maksim], Thanks for the initial investigation and review.

> Data entries looped in CDC if ExpirePolicy is set 
> --------------------------------------------------
>
>                 Key: IGNITE-21285
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21285
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Maksim Timonin
>            Assignee: Nikita Amelchev
>            Priority: Major
>              Labels: ise
>             Fix For: 2.17
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In case ExpirePolicy is used, than in CacheVersionConflictResolverImpl#resolve used the Merge strategy to set TTL and EXPIRE for the conflicted entry.
> If the entry received from other dataCenter it marked as merged and later its original version is ignored.
> See IgniteTxLocalAdapter#userCommit:672L:
>  # It replace explicitVer (set to original version) with local transaction version `explicitVer = writeVersion()`
>  # Later its set as conflict version {{txEntry.conflictVersion(explicitVer)}}
>  # `GridCacheVersionEx#addConflictVersion` return the tx version as it now equals to the conflict version
>  
> Reproducer [https://github.com/apache/ignite-extensions/pull/254]



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