cshannon commented on PR #3418: URL: https://github.com/apache/accumulo/pull/3418#issuecomment-1573682533
> This looks good. I have not reviewed everything, still want to look over the testing changes. I should be able to do that tomorrow. Sounds good. So we could in theory start merging in these no-chop merge changes this into main as they are finished/read as long as it wouldn't break existing behavior (and this doesn't as the fencing won't be used yet). But I am leaning more towards the option of creating another branch in the repo that we can use for no-chop merge changes like this and follow on PRs. (just like we have one for elasticity). I figure once things look good, then we can merge everything back to main. This seems like the best approach for now as I'm hesitant to merge anything into main yet until more follow on work is complete, like updates to how we store metadata and actual merge algorithm changes, because things are likely to need to be tweaked a bit. Also I think all of this stuff should be targeted for after 3.0 (3.1 if that is the next version). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
