milleruntime commented on issue #1872: URL: https://github.com/apache/accumulo/issues/1872#issuecomment-767566557
> When you say client, are you thinking the shell? How would you handle this for automated clients? Feedback could be an intermediate step, but I think the desired behavior in almost all cases would be to terminate any outstanding operations and delete as quickly as possible. I was thinking of adding to the API, which could definitely be added to the Shell as a new command. We could add another API method (similar to how `flush` evolved) to evolve the current delete method. In TableOperations.java: ` @Deprecated void delete(String tableName)` `@since 2.1 void delete(String tableName, boolean wait)` > Is there any value in waiting for a compaction to complete if the next thing to happen is that the table / file is deleted? No that I know of but perhaps Keith may know of a reason. There are checks in place for the compaction to cancel (see Keith's comments above) but I don't think they are foolproof since it depends on where along in the compaction process the delete occurs. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
