You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2013/04/10 16:36:16 UTC
[jira] [Commented] (ACCUMULO-1256) Add table trash can
[ https://issues.apache.org/jira/browse/ACCUMULO-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627840#comment-13627840 ]
John Vines commented on ACCUMULO-1256:
--------------------------------------
I think all properties and permissions should be maintained. Fundamentally, I think this boils down to simply having a special trash state for a table before it goes through the real delete. One option for naming conflicts is including a timestamp in the name of the table for when it was deleted as a way to identify which one to users.
And perhaps all trash tables should be listed somewhere in the monitor, in a different table. I don't think it should be in the same table as Online and Offline tables.
> 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