[GitHub] [accumulo] cshannon commented on issue #1327: No-chop merges

["cshannon (via GitHub)" <gi...@apache.org>]

cshannon commented on issue #1327:
URL: https://github.com/apache/accumulo/issues/1327#issuecomment-1416772087

   I have started looking into this and doing research on how to go about implementing it. I plan to try and break this up into sub-tasks to implement smaller changes at a time. Some things of course won't be possible in isolation but I will break it up the best I can.  Also, because of the scope of the issue I don't see it being ready for 3.0.0 so should we un-assign this from 3.0.0? I could see some smaller changes being done for 3.0.0 but probably not the entire feature.
   
   Also, one question I had as I've been diving into this is will the goal here to be to ONLY  support no-chop merges or is there a desire to preserve the current behavior of merges (maybe a flag or something to specify the type)? 
   
   I could see scenarios where a user would want to actually do a merge the current way (and take the performance penalty that comes with it) but I'm thinking we probably don't need to preserve the current merge strategy as an option because a user could also just simply run a compaction after a merge and accomplish the same thing if desired.


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org