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 15:00:23 GMT


Keith Turner commented on ACCUMULO-1256:

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

Yeah, maybe another page with a table showing how much space each table in the trash can is
consuming and how many entries it has.  I think space usage is the main thing a user would
want to know about a table in the trash can.  Is there anything else a user would like to
know?  This make me think that a user may want to delete a table in the trash can before it
ages off.  I suppose if delete table is called with the name of a table that is already in
the trash can that it could go ahead and really delete it.
> 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