phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4530) Do not collect delete markers during major compaction of table with disabled mutable indexes
Date Wed, 17 Jan 2018 00:04:00 GMT

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

James Taylor updated PHOENIX-4530:
----------------------------------
    Description: 
If major compaction occurs on a table with mutable indexes that have the INDEX_DISABLE_TIMESTAMP
set, we currently permanently disable the index, forcing it to be manually rebuilt from scratch.
This is to prevent it from potentially being corrupted as we need the delete markers to remain
in order to guarantee the data table and index table remain in sync.

An alternate approach (mentioned by [~ankit@apache.org] during review) is to detect this case
in a pre-compaction hook and set the compaction up so that delete markers are not removed.
This would have the advantage that we wouldn't have to permanently disable the index and rebuild
it from scratch.

> Do not collect delete markers during major compaction of table with disabled mutable
indexes
> --------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4530
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4530
>             Project: Phoenix
>          Issue Type: Improvement
>         Environment: If major compaction occurs on a table with mutable indexes that
have the INDEX_DISABLE_TIMESTAMP set, we currently permanently disable the index, forcing
it to be manually rebuilt from scratch. This is to prevent it from potentially being corrupted
as we need the delete markers to remain in order to guarantee the data table and index table
remain in sync.
> An alternate approach (mentioned by [~ankit@apache.org] during review) is to detect this
case in a pre-compaction hook and set the compaction up so that delete markers are not removed.
This would have the advantage that we wouldn't have to permanently disable the index and rebuild
it from scratch.
>            Reporter: James Taylor
>            Priority: Major
>
> If major compaction occurs on a table with mutable indexes that have the INDEX_DISABLE_TIMESTAMP
set, we currently permanently disable the index, forcing it to be manually rebuilt from scratch.
This is to prevent it from potentially being corrupted as we need the delete markers to remain
in order to guarantee the data table and index table remain in sync.
> An alternate approach (mentioned by [~ankit@apache.org] during review) is to detect this
case in a pre-compaction hook and set the compaction up so that delete markers are not removed.
This would have the advantage that we wouldn't have to permanently disable the index and rebuild
it from scratch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message