[
https://issues.apache.org/jira/browse/HBASE-28897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889999#comment-17889999
]
Nick Dimiduk commented on HBASE-28897:
--------------------------------------
[~rmdmattingly] you need to set the "fixVersions" field with the branches to
which this was committed -- this will always be an "unreleased" version. The
"affectsVersion" field is for things like bug reports, that impact this or that
specific release version -- this is always a "released" version. Also, no need
to set "fixVersion" as 4.0 when it's also applied to branch-3, which has not
seen a release yet.
> Force CF compatibility during incremental backup
> -------------------------------------------------
>
> Key: HBASE-28897
> URL: https://issues.apache.org/jira/browse/HBASE-28897
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
> Affects Versions: 3.0.0-beta-1, 4.0.0-alpha-1, 2.7.0, 2.6.2
> Reporter: Hernan Gelaf-Romer
> Assignee: Hernan Gelaf-Romer
> Priority: Major
> Labels: pull-request-available
>
> 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)
