ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10130) Add option for disable triggering cache interceptor in case of conflicts.
Date Thu, 20 Dec 2018 08:54:00 GMT

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

Alexey Goncharuk commented on IGNITE-10130:
-------------------------------------------

[~antonovsergey93], please make the flag to be non-static, it will be impossible to change
this property in tests. Otherwise looks good.

> Add option for disable triggering cache interceptor in case of conflicts.
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-10130
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10130
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Sergey Antonov
>            Assignee: Sergey Antonov
>            Priority: Major
>             Fix For: 2.8
>
>
> Interceptor semantic for Dr updates looks broken.
> For now, Ignite call post-update interceptor methods for Dr updates and there is no way
to disable interceptor calls at all.
> This force user to call onGet before sending entry to remote DR that may be inefficient.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message