You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/04/15 11:19:25 UTC
[jira] [Resolved] (IGNITE-3007) Get rid of "State" object in
GridNearAtomicUpdateFuture.
[ https://issues.apache.org/jira/browse/IGNITE-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov resolved IGNITE-3007.
-------------------------------------
Resolution: Fixed
> Get rid of "State" object in GridNearAtomicUpdateFuture.
> --------------------------------------------------------
>
> Key: IGNITE-3007
> URL: https://issues.apache.org/jira/browse/IGNITE-3007
> Project: Ignite
> Issue Type: Task
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> *Problem*
> Currently {{GridNearAtomicUpdateFuture}} has {{State}} inner class. It's state is used as monitor for advanced synchronization.
> We are going to implement dedicated future for single key-value pair update, which will try reusing as much code from {{GridNearAtomicUpdateFuture}} as possible. This "state" will make it harder.
> *Solution*
> Remove {{State}} class and use dedicated "new Object()" as monitor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)