You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2017/04/19 00:47:41 UTC
[jira] [Updated] (PHOENIX-3796) LocalIndexes apply the entire batch
for each mutation in a batch
[ https://issues.apache.org/jira/browse/PHOENIX-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated PHOENIX-3796:
-----------------------------------
Attachment: 3796-4x.txt
Here's a proposed patch (also fixes PHOENIX-3789 in a simpler way).
The idea is to simply apply both local and remote index update the first time we update an index, then mark the batch as done.
> LocalIndexes apply the entire batch for each mutation in a batch
> ----------------------------------------------------------------
>
> Key: PHOENIX-3796
> URL: https://issues.apache.org/jira/browse/PHOENIX-3796
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: 3796-4x.txt
>
>
> [~mujtabachohan] pointed out an "exponential" increase in update time in the size of the batch.
> Indeed when I look at the code in Indexer.java I see that for each call to postPut or postDelete we do insert the entire into the local index. (So for a batch of size 10000 we'd make 10000 index updates 10000 times)
> [~rajeshbabu]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)