[
https://issues.apache.org/jira/browse/PHOENIX-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3953:
----------------------------------
Description: 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. (was: 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. At this point, a manual rebuild of the index would be required.)
> 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
> Labels: globalMutableSecondaryIndex
>
> 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)
