[
https://issues.apache.org/jira/browse/IGNITE-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727345#comment-16727345
]
Ignite TC Bot commented on IGNITE-10130:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC JDBC{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2620950]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2613533&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
