accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corey J. Nolet (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1256) Add trash can for deleted tables
Date Wed, 22 May 2013 01:34:21 GMT


Corey J. Nolet commented on ACCUMULO-1256:

I can see a case where a user will create a table, delete the table, create again a table
of the same name, and delete it. In your design both tables of name "x" will be preserved
in the trash because they are given unique names. I like your point about being able to call
"du" on the table in the trash but do you have any ideas surrounding any other means of a
user being able differentiate between the tables in the client API? Are you thinking that
trashed tables may still show up to some capacity in the monitor?
> Add trash can for deleted tables
> --------------------------------
>                 Key: ACCUMULO-1256
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>            Reporter: Keith Turner
>              Labels: gsoc2013, mentor, newbie
>         Attachments: ACCUMULO-1256-proposal-01.html, ACCUMULO-1256-proposal-01.txt
> 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