[
https://issues.apache.org/jira/browse/ACCUMULO-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627874#comment-13627874
]
Keith Turner commented on ACCUMULO-1256:
----------------------------------------
bq. Do we need a special state? Could we just have trashed tables be offline
tables with a particular naming convention?
Offline tables can be exported and map reduced over. I think we would not want
to support this for tables in the trash can. I am thinking tables in the trash
can should be completely invisible to the rest of the API, except for when the
user explicitly ask for a list of tables in the trash. So if someone tries to
export a table in the trash can, they should get an exception. Exporting a
table in the trash would not be useful, the table could be deleted while a
distcp is happening.
> Add table trash can
> -------------------
>
> Key: ACCUMULO-1256
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1256
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Keith Turner
>
> It may be useful to provide an optional trash feature. If this feature were
> enabled, then when a table is deleted it would go into the trash can. Tables
> that had been in the trash for a while could would eventually be deleted.
> Tables could be undeleted from the trash can.
> What would the API and shell commands look like? How would multiple tables
> in the trash can with the same name be handled in the API? Would/should per
> table properties and pertable permissions be preserved? Should these tables
> in the trash can show up in the monitor in some way?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
