accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1256) Add table trash can
Date Wed, 10 Apr 2013 15:10:16 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627882#comment-13627882
] 

John Vines 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?

Technically we could, but we already have a state model for the tables, it would be silly
to break out of the model for a new feature. It could end up leading to odd state changes
that we may inadvertently introduce down the road.
                
> 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

Mime
View raw message