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 2017/02/03 13:00:53 UTC

[jira] [Updated] (IGNITE-4652) Optimization: implement BPlusTree.invoke

     [ https://issues.apache.org/jira/browse/IGNITE-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Semen Boikov updated IGNITE-4652:
---------------------------------
    Description: Currently for atomic cache update we first read previous cache value (BPlusTree.find), then depending on some cache logic can do put or remove (BPlusTree.put/remove). It is possible to get rid of first BPlusTree.find if BPlusTree provide 'invoke' operation similar to IgnteCache.invoke.

> Optimization: implement BPlusTree.invoke
> ----------------------------------------
>
>                 Key: IGNITE-4652
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4652
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Semen Boikov
>             Fix For: 2.0
>
>
> Currently for atomic cache update we first read previous cache value (BPlusTree.find), then depending on some cache logic can do put or remove (BPlusTree.put/remove). It is possible to get rid of first BPlusTree.find if BPlusTree provide 'invoke' operation similar to IgnteCache.invoke.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)