You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2024/10/08 14:07:00 UTC

[jira] [Updated] (HBASE-28897) Incremental backups can be taken with incompatible column families

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

Nick Dimiduk updated HBASE-28897:
---------------------------------
    Issue Type: Bug  (was: Improvement)

> Incremental backups can be taken with incompatible column families
> ------------------------------------------------------------------
>
>                 Key: HBASE-28897
>                 URL: https://issues.apache.org/jira/browse/HBASE-28897
>             Project: HBase
>          Issue Type: Bug
>          Components: backup&amp;restore
>            Reporter: Hernan Gelaf-Romer
>            Assignee: Hernan Gelaf-Romer
>            Priority: Major
>
> Incremental backups can be taken even if the table descriptor of the current table does not match the column families of the full backup for that same table. When restoring the table, we choose to use the families of the full backup. This can cause the restore process to fail if we add a column family in the incremental backup that doesn't exist in the full backup. The bulkload process will fail because it is trying to write column families that don't exist in the restore table. 
>  
> I think the correct solution here is to prevent incremental backups from being taken if the families of the current table don't match those of the full backup. This will force users to instead take a full backup.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)