[
https://issues.apache.org/jira/browse/PHOENIX-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973903#comment-15973903
]
Rajeshbabu Chintaguntla commented on PHOENIX-3796:
--------------------------------------------------
[~lhofhansl] [~jamestaylor] It's very bad bug. Sorry for this. Because mvcc
blocking the local updates in postBatchMutate moved writing local index updates
to postPut/Delete but missed to take care of writing once. So moving local
index writes to postBatchMutateIndispensably hook makes very sense(After
HBASE-15600 we don't need this at all). But completely moving index writes to
postBatchMutateIndispensably won't make index data out of sync with actual data
in case of parallel writes?
> 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)
