Skip to content

Conversation

@DomGarguilo
Copy link
Member

The TableOperations methods get and setTabletAvailability accepted a Range as a parameter but only treated it as a range of rows. The changes in this PR make that intent more explicit and use a more specific type as the input param.

@DomGarguilo DomGarguilo added this to the 4.0.0 milestone Oct 6, 2025
@DomGarguilo DomGarguilo self-assigned this Oct 6, 2025
* portion of the start and end Keys and the inclusivity parameters are used when determining the
* range of affected tablets. The other portions of the start and end Keys are not used.
* for the tablets to reach this availability state. The supplied row range is compared against
* the tablets' start/end rows using its lower/upper bounds and inclusivity flags; any non-row
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still needed any non-row portions of the keys are ignored. ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea good catch I guess using RowRange makes that explicit here so we don't need to explain it.

Removed redundant information about non-row portions of keys in the Javadoc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants