accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1256) Add table trash can
Date Wed, 10 Apr 2013 14:46:17 GMT


Keith Turner commented on ACCUMULO-1256:

bq.  I think this boils down to simply having a special trash state for a table before it
goes through the real delete

I think thats the right approach.  Want to do things in such a way that a new table can be
created with the same name as a table in the trash can.

bq. 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.

OK. So maybe deleted tables in the trash can could have names like the following?


Users would see these names when listing deleted tables and would use that name to undelete.
  The '.' dot chars are reserved and can not be used in a table name, so we would not have
to worry about a user creating a table with this name used in the trash can.
> Add table trash can
> -------------------
>                 Key: ACCUMULO-1256
>                 URL:
>             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
> 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:

View raw message