cshannon commented on PR #3328: URL: https://github.com/apache/accumulo/pull/3328#issuecomment-1518267246
> @cshannon, interesting ideas. I am planning to move these changes to target 3.1. I will also look into the other ideas as I go. Sounds good, there's no rush. I can and will keep using Range in my no-chop merge prototype for now as it would be easy to swap it out if/when a RowRange object is ready if it supported all the utility methods as I said. I can also review this too and look more at it to help out. In theory this object should be able to be re-worked from the existing Range object and support the existing methods (even if it's just a shared interface or something and not inheritance) because supporting only rows should be simpler logic to implement than the existing object that handles an entire Key. -- 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]
