[
https://issues.apache.org/jira/browse/HBASE-29240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HBASE-29240:
-----------------------------------
Labels: pull-request-available (was: )
> Backup ancestry trees should have the ability to be invalidated
> ---------------------------------------------------------------
>
> Key: HBASE-29240
> URL: https://issues.apache.org/jira/browse/HBASE-29240
> Project: HBase
> Issue Type: Improvement
> Components: backup&restore
> Reporter: Hernan Gelaf-Romer
> Assignee: Hernan Gelaf-Romer
> Priority: Major
> Labels: pull-request-available
>
> To improve backup consistency, it should be possible to invalidate the
> ancestry tree for a modern backup, prompting the operator to perform a full
> backup.
> One practical use case for this enhancement is handling table truncation more
> effectively. Currently, if a full backup is taken, a table is truncated, new
> data is written, and an incremental backup is triggered, restoring the backup
> will include both pre-truncation and post-truncation data.
> To address this issue, the ancestry tree should be invalidated whenever a
> table is truncated. This will enforce the creation of a new full backup,
> ensuring consistency during the restore process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
