[
https://issues.apache.org/jira/browse/KUDU-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850236#comment-16850236
]
Mike Percy commented on KUDU-2827:
----------------------------------
To add a little more context to this Jira, the implication is that we should
have a way to determine whether a table was dropped or renamed, which would
likely require additional master RPC API support, since we would need to be
able to take a look at the current state of a table id. Table ids are used in
the backup graph. The purpose is to properly handle dropped tables in the
backup GC (backup cleanup) tool now merged as part ofÂ
[https://github.com/apache/kudu/commit/a5a8da655ca8f0088dcd39301bd9bd87e182c460]
> Backup should tombstone dropped tables
> --------------------------------------
>
> Key: KUDU-2827
> URL: https://issues.apache.org/jira/browse/KUDU-2827
> Project: Kudu
> Issue Type: Task
> Components: backup
> Reporter: Mike Percy
> Priority: Major
>
> It would be useful for backup to "tombstone" dropped tables so that the GC
> process can detect this and eventually consider these eligible for deletion,
> even though they are still on the restore path from a backup graph
> perspective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
