DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
Apache Accumulo is a highly scalable structured store based on Google’s BigTable. Accumulo is written in Java and operates over the HDFS (Hadoop Distributed File System). It is a richer data model than key-value stores. Yet, it is not a fully relational database. Accumulo provides efficient storage and retrieval of structured data and the support for Accumulo tables to be used as input/output in MapReduce operations. It features automatic load-balancing and partitioning, data compression and fine-grained security labels.
The goal of this proposal is to enable a trash can facility in Accumulo. When enabled, the tables which are deleted are treated by the rest of Accumulo as deleted. Yet, it should be possible to restore these tables to its original state and name at a later time. They should not appear in client operations that list tables. When an access is attempted to a trash table, a TableDeletedException should be thrown.
2. Detailed description
2.1 New "TRASH" State
For accommodating trashing in Accumulo, a new state called TRASH \called TRASH [1\] should be added to the existing list of states viz, NEW, ONLINE, OFFLINE, DELETING, UNKNOWN. This can be added in in Wiki Markup
- org.apache.accumulo.core.master.state.tables.TableState
...
- general.trash.enable - Used to enable trashing feature in Accumulo. Can be done at runtime without restarts
- general.trash.timeout - Used to set the maximum time after which the tables in trash will be deleted automatically
- general.trash.maxspace - Used to set the maximum space allotted for tables in trash. When the space is exceeded, the table with oldest delete timestamp can be discarded to make space.
2.
...
5 API
New methods can be added to the supported table operations. These can be added to the interface TableOperations:
...
August 05 - September 09
Implementation of the new FATE operation undelete state "TRASH" and new FATE operations undelete and listTrash() and changes to the delete table operation.
September 13
Midterm evaluation
September 14 - October 21
Implementation of the timeout feature in the master. Addition of configuration properties.
October 28
Submitting final evaluation