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 2017/10/23 11:46:00 UTC

[jira] [Commented] (IGNITE-6701) Do not deserialize previous value during indexes update

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

Vladimir Ozerov commented on IGNITE-6701:
-----------------------------------------

[~sboikov], also the same problem is applicable for remove operation: {{GridH2IndexBase#removex}} is implemented through {{GridH2IndexBase#remove}} which also causes deserialization.

> Do not deserialize previous value during indexes update
> -------------------------------------------------------
>
>                 Key: IGNITE-6701
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6701
>             Project: Ignite
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>          Components: sql
>            Reporter: Semen Boikov
>              Labels: iep-1, performance
>             Fix For: 2.4
>
>
> In GridH2Table.doUpdate all indexes are updated using BPlusTree.put method which deserializes previous value, actually previous value is already available in GridQueryProcessor.store/remove methods. Need try to change GridH2Table.doUpdate to use BPlusTree.putx instead of BPlusTree.put.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)