DomGarguilo commented on PR #3342: URL: https://github.com/apache/accumulo/pull/3342#issuecomment-3238029214
> For the new APIs in 4.0 [setTabletAvailability](https://github.com/apache/accumulo/blob/068a565c8406b1195c8ea293b1044d28cc9d67e9/core/src/main/java/org/apache/accumulo/core/client/admin/TableOperations.java#L1053) and [getTabletInformation](https://github.com/apache/accumulo/blob/068a565c8406b1195c8ea293b1044d28cc9d67e9/core/src/main/java/org/apache/accumulo/core/client/admin/TableOperations.java#L1066) this row range would be useful. Also it may make #5788 easier if the API took a row range instead of a key range, the key range make the code for dealing w/ ranges in the impl more complex. The new APIs in this look good to me, is there anything holding this back? I don't really remember if there was anything specific holding this back. I think @ctubbsii had some input initially about these changes in general but its been so long another look might be necessary to get reacquainted with whats going on here. I do remember some discussing about using Guava (I think) Range object instead of creating our own that functions very similar but I'll have to look into everything again. -- 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]
