accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1256) Add trash can for deleted tables
Date Wed, 22 May 2013 15:47:21 GMT

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

Keith Turner commented on ACCUMULO-1256:
----------------------------------------

bq.  I like your point about being able to call "du" on the table in the trash

I just looked through TableOperations and did not see any other API calls that should work
w/ a table in trash.  If anyone else can think of any other exceptions, it would be nice to
identify these now.  

bq. do you have any ideas surrounding any other means of a user being able differentiate between
the tables in the client API?

Do you mean if the user calls listTrash() and they see trash-foo-2013052201-01 and trash-foo-2013052202-01,
how would they know which foo to undelete?  I was thinking they would use the date.

bq. Are you thinking that trashed tables may still show up to some capacity in the monitor?

I think users will need an easy way to see what is in trash and how much space is used.  This
could be in the monitor, shell, or both.  In the shell we could possibly add a flag to the
du command to analyze space usage by tables in the trash.  This would save the user the hassle
of getting a list of tables in trash and calling du.  What other capabilities users will need
to manage this feature?  It seems like a way to delete all tables in the trash would be useful,
a way to empty the trash.
                
> Add trash can for deleted tables
> --------------------------------
>
>                 Key: ACCUMULO-1256
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1256
>             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
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