You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/01/22 14:31:39 UTC

[jira] [Commented] (IGNITE-2434) Ignite updates cache store even if EntryProcessor did not update cache entry

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

ASF GitHub Bot commented on IGNITE-2434:
----------------------------------------

GitHub user agoncharuk opened a pull request:

    https://github.com/apache/ignite/pull/418

    IGNITE-2434 - Do not update cache store if entry processor was a noop.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/agoncharuk/ignite ignite-2434

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/418.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #418
    
----
commit 20282071e3a85673c30a65c67262fb6c1d796579
Author: Alexey Goncharuk <al...@gmail.com>
Date:   2016-01-22T13:30:32Z

    IGNITE-2434 - Fixing the test.

----


> Ignite updates cache store even if EntryProcessor did not update cache entry
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-2434
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2434
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Goncharuk
>             Fix For: 1.6
>
>
> org.apache.ignite.internal.processors.cache.store.IgniteCacheWriteBehindNoUpdateSelfTest was added to master.



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