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/09/05 17:24:00 UTC

[jira] [Commented] (PHOENIX-3953) Clear INDEX_DISABLED_TIMESTAMP and disable index on compaction

    [ https://issues.apache.org/jira/browse/PHOENIX-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154027#comment-16154027 ] 

Lars Hofhansl commented on PHOENIX-3953:
----------------------------------------

Does this mean we're writing to another table (to a region most likely located on a different server) from inside the compaction hooks? That sounds scary. Does it fail gracefully, i.e. letting the compaction finish?

> 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.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)