[
https://issues.apache.org/jira/browse/PHOENIX-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149104#comment-15149104
]
Hudson commented on PHOENIX-2635:
---------------------------------
SUCCESS: Integrated in Phoenix-master #1140 (See
[https://builds.apache.org/job/Phoenix-master/1140/])
PHOENIX-2635 Partial index rebuild doesn't work for mutable data (jtaylor: rev
4ccce0ed103db04667da95ab515eda76029dacdb)
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataRegionObserver.java
> Partial index rebuild doesn't work for mutable data
> ---------------------------------------------------
>
> Key: PHOENIX-2635
> URL: https://issues.apache.org/jira/browse/PHOENIX-2635
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2635.patch, PHOENIX-2635_addendum.patch,
> PHOENIX-2635_v2.patch, PHOENIX-2635_v3.patch
>
>
> The partial rebuild index feature for mutable secondary indexes does not do
> the correct index maintenance. We currently only insert the new index rows
> based on the current data row values which would not correctly remove the
> previous index row (thus leading to an invalid index). Instead, we should
> replay the data row mutations so that the coprocessors generate the correct
> deletes and updates.
> Also, instead of *every* region running the partial index rebuild, we should
> have each region only replay their own data mutations so that we're not
> duplicating work.
> A third (and perhaps most serious) issue is that the partial index rebuild
> could trigger the upgrade code before a cluster is ready to be upgraded.
> We'll definitely want to prevent that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
