[
https://issues.apache.org/jira/browse/IGNITE-22420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-22420:
------------------------------------
Description:
There is a wrong behavior for checking ExpirePolicy for thin clients handling
`putAllConflict()`.
`cache.getExpiryPolicy()` never returns null and then this is not a right way
to check it. Instead get value of expireTime of the entry is better.
This case was already fixed for thick clients, see ignite-extensions (cdc-ext)
in the commit:
[https://github.com/apache/ignite-extensions/commit/f6ee5b316fa1307dea2e8c8f96d1072bae875b22]
> Data replicated with a thin client fails if contains mixed expiry policy
> ------------------------------------------------------------------------
>
> Key: IGNITE-22420
> URL: https://issues.apache.org/jira/browse/IGNITE-22420
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is a wrong behavior for checking ExpirePolicy for thin clients handling
> `putAllConflict()`.
> `cache.getExpiryPolicy()` never returns null and then this is not a right way
> to check it. Instead get value of expireTime of the entry is better.
> This case was already fixed for thick clients, see ignite-extensions
> (cdc-ext) in the commit:
> [https://github.com/apache/ignite-extensions/commit/f6ee5b316fa1307dea2e8c8f96d1072bae875b22]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
