[GitHub] [accumulo] milleruntime edited a comment on issue #1998: Decide behavior of external compactions when a table is taken offline.

[GitBox <gi...@apache.org>]

milleruntime edited a comment on issue #1998:
URL: https://github.com/apache/accumulo/issues/1998#issuecomment-817946992


   We will have to take in consideration all offline operations as they currently make assumptions about the state of the table when it is offline. For example, An Admin offlines a table in order to perform an exportTable. The exportTable behavior will now have to take in consideration external compactions. Ideally, this new consideration won't make the Admin's life more difficult.  
   
   If we allow external compactions to continue when a table is offline, I think we will also have to modify all the offline operations to check for running external compactions and handle them in some way. I have no idea how difficult this would be as offline behavior is rather mysterious and elusively sprinkled across different operations. For example, a new table created offline probably won't be affected but I am not sure about exportTable, table clone, bulk imports, or the offline scan map reduce option. Also didn't we add offline splits in 2.0 as well?


-- 
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:
users@infra.apache.org