-
Notifications
You must be signed in to change notification settings - Fork 21
CNDB-16289: switch index hints limit to use Short.MAX_VALUE #2174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Checklist before you submit for review
|
|
The coordinator will always validate that the indexes mentioned by the index hints exist in the schema, and there cannot be repeated index in the hints because the hints are disjoint sets. So the number of index hints is implicitly limited by the number of existing indexes. I don't see why we should check a guardrail to limit the number of hints. Maybe a reason could be that the guardrail has changed to a value lower than the number of existing indexes? But even in that case it's odd to use the guardrail for SAI when the hints could contain other indexes. I think if we want to use a guardrail we could instead count the number of hints referencing an index of each kind and apply the relevant guardrail. |
|
Updated to bring this in line with main, checking |
adelapena
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, +1.
|
❌ Build ds-cassandra-pr-gate/PR-2174 rejected by Butler7 regressions found Found 7 new test failures
Found 3 known test failures |



What is the issue
Currently
maxIncludedOrExcludedIndexCountis usinggetSecondaryIndexesPerTableFailThresholdbut the coordinator will always validate that the indexes mentioned by the index hints exist in the schema, and there cannot be repeated index in the hints because the hints are disjoint sets. So the number of index hints is implicitly limited by the number of existing indexes, therefore we should use Short.MAX_VALUE like main does.What does this PR fix and why was it fixed
Change the index hint limit to use Short.MAX_VALUE