Besides using the tableOperations to deleteRows or delete the table entirely, what is the fastest way to delete all data in a table? I am currently using a BatchDeleter but it is extremely slow when I have a large amount of data. Any better options?
I don't want to use the tableOperations because both the deleteRows and delete blow away the splits. I would like to keep the splits in place.
Thanks for your response. I have a variety of unit tests. For each unit test, I insert and search for certain data. I don't want data from the previous unit test to be present in the table.
The main issue is that I can't delete the table nor can I create a new one because of my tablet balancer. If I do, the splits won't be applied properly. The table needs to exist and be split properly when Accumulo starts up.
I don't think this has been directly said, but setting DevNull or an age off iterator compaction time will mean you have to read all of your data. You're doing it in parallel, but still evaluating all the data against the iterator.
Also, are you trying to do this with 0 downtime-- ie, will clients write data during the compaction period? I think that might cause issues if another compaction is queued while you have DevNull set as the compaction iterator, and possibly age off. On Mon, May 12, 2014 at 12:57 PM, BlackJack76 <[EMAIL PROTECTED]> wrote:
Also, I apologize for the second reply but wanted to touch on your last point. I am fairly new to the Accumulo community and not really sure how or what the process is for submitting a patch or updating any documentation. I would be happy to contribute but just don't have the know how. Thanks again!