[
https://issues.apache.org/jira/browse/KUDU-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913009#comment-16913009
]
Yingchun Lai commented on KUDU-2919:
------------------------------------
For Adar's advice, how to rollback a table after it has been "trashed"?
Another simple approach I'm considering is, a "trashed" table is unvisible by
client, but we can use CLI tool to check it. Masters can reserve it for some
period of time, e.g. 7 days, configurable by gflag. And also we can use CLI
tool to "recall" this kind of table.
Another question, if we want to create the same table name or the same bounds
tablets as the one which has been trashed, how to deal with it?
> It's useful to support trash while drop partition/tables
> --------------------------------------------------------
>
> Key: KUDU-2919
> URL: https://issues.apache.org/jira/browse/KUDU-2919
> Project: Kudu
> Issue Type: New Feature
> Reporter: HeLifu
> Priority: Major
>
> In order to shorten the recovery time of erroneously dropped partitions or
> tables, it's useful to support trash functionality. For example, when we use
> synchronization tools like sqoop to synchronize data from DBMS to kudu, if
> the synchronized table(partitions) is dropped unexpectedly, it will take a
> long time to re-synchronize the data in full.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
