You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2016/08/29 14:00:27 UTC

[jira] [Commented] (IGNITE-3164) Add an option to send resulting value instead of entry processor in transactional cache

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

Semen Boikov commented on IGNITE-3164:
--------------------------------------

Looks like fix for https://issues.apache.org/jira/browse/IGNITE-3471 will affect the same code. Need check if it is possible to fix IGNITE-3471 as part of this issue.

> Add an option to send resulting value instead of entry processor in transactional cache
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3164
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3164
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Nikolay Tikhonov
>              Labels: important
>             Fix For: 1.8
>
>
> In some cases user can't guarantee that EP behaves consistently on all nodes. In transactional cache this can lead to inconsistent cache, because we invoke EP on both primary and backup nodes.
> We can add {{withSendValueToBackup()}} flag (naming is arguable) which will override current default behavior.
> We also need to update documentation, especially provide the explanation of EP behavior in atomic and transactional caches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)