[
https://issues.apache.org/jira/browse/IGNITE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557525#comment-14557525
]
Thiago Souza commented on IGNITE-881:
-------------------------------------
I would like to start contributing to Ignite through this issue.
But I've got a question, the current implementation in
DataStructuresCommandHandler takes "initial" and "delta" as arguments while the
commands in GridCacheCommandHandler takes "val" and "val2", how should I adapt
this?
> Refactor ATOMIC_INCREMENT and ATOMIC_DECREMENT REST commands to use entry
> processor
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-881
> URL: https://issues.apache.org/jira/browse/IGNITE-881
> Project: Ignite
> Issue Type: Task
> Components: newbie
> Reporter: Yakov Zhdanov
>
> Currently, these commands alter the state of CacheAtomicLong, but they will
> be more flexible if they atomically change cache key-value mapping.
> Consider the following:
> # Move handling logic to GridCacheCommandHandler
> # Whenever command is received handling node should call
> {{org.apache.ignite.IgniteCache#invoke(K,
> org.apache.ignite.cache.CacheEntryProcessor<K,V,T>, java.lang.Object...)}} to
> properly change the value (depending on the argument) and return result
> # If value is not a Number, error should be returned to the caller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
