ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6701) Do not deserialize previous value during indexes update
Date Tue, 07 Nov 2017 14:19:00 GMT

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

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

Test run with latest changes: https://ci.ignite.apache.org/viewQueued.html?itemId=932473

> 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
>            Assignee: Roman Kondakov
>              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)

Mime
View raw message