You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2019/12/20 02:13:00 UTC

[jira] [Updated] (PHOENIX-5645) GlobalIndexChecker should prevent compaction from purging very recent deleted cells

     [ https://issues.apache.org/jira/browse/PHOENIX-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby updated PHOENIX-5645:
-------------------------------------
    Summary: GlobalIndexChecker should prevent compaction from purging very recent deleted cells  (was: GlobalIndexChecker should prevent compaction from purging vey recent deleted cells)

> GlobalIndexChecker should prevent compaction from purging very recent deleted cells
> -----------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5645
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5645
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>
> IndexTool rebuilds and index scrutiny can both give strange, incorrect results if a major compaction occurs in the middle of their run. In the rebuild case, it's because we're rewriting "history" on the index at the same time that compaction is rewriting "history" by purging deleted and expired cells. 
> In the case of scrutiny, it's because it does an SCN-based lookback, and if versions are purged on the index before their equivalent data table rows, you can get false errors. 
> Since in the new indexing path we already have a coprocessor on each index, it should override the compaction hook to shield rows newer than some configurable age from being purged during a major compaction.
> In the future, this should be contributed as a general feature to HBase for arbitrary tables. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)