[
https://issues.apache.org/jira/browse/PHOENIX-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3953:
----------------------------------
Attachment: PHOENIX-3953_addendum1.patch
Please review, [~samarthjain] or [~vincentpoon]. Vincent and I thought of a
case where compaction of the index table while waiting for the rebuilder can be
problematic (see code comment). So now we disable index in both cases: if data
table is major compacted or index table is major compacted. Note that we
piggyback on the RPC already being done to get the GUIDE_POSTS_WIDTH so we
don't have to do yet another one at compaction time.
> Clear INDEX_DISABLED_TIMESTAMP and disable index on compaction
> --------------------------------------------------------------
>
> Key: PHOENIX-3953
> URL: https://issues.apache.org/jira/browse/PHOENIX-3953
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Labels: globalMutableSecondaryIndex
> Fix For: 4.12.0
>
> Attachments: PHOENIX-3953_addendum1.patch, PHOENIX-3953.patch,
> PHOENIX-3953_v2.patch
>
>
> To guard against a compaction occurring (which would potentially clear delete
> markers and puts that the partial index rebuild process counts on to properly
> catch up an index with the data table), we should clear the
> INDEX_DISABLED_TIMESTAMP and mark the index as disabled. This could be done
> in the post compaction coprocessor hook. At this point, a manual rebuild of
> the index would be required.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
