-
Notifications
You must be signed in to change notification settings - Fork 21
CNDB-13534: Add RequestFailureReason.FEATURE_NEEDS_INDEX_REBUILD #1781
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
base: main-5.0
Are you sure you want to change the base?
Conversation
I looked at the test failures reported above by Butler and they all look like known failing or flaky tests on the 5.0 test failure list I don't think Butler knows how to do a correct comparison with One thing, if you didn't do it already, is to run the "verify" script that I think I mentioned previously - it identified all the unit and distributed tests that were touched by the most recent commit and executes them. For a relatively large commit like this, that's my typical method of verifying the port |
I checked out the branch and got a compile error:
Then I realized the CI build has the same error - weird that it ran tests if the build part had a problem 🤷🏻 |
I think that was because your commits got in and caused a small conflict that I resolved in the web interface. I've rebased and pushed it now. |
The new request failure reason should be used when the on-disk format of an index in a replica doesn't support a requested feature. Also, rename org.apache.cassandra.index.sai.disk.format.Version.latest() to Version.current(), and add separate Version.CURRENT and Version.LATEST constants.
|
❌ Build ds-cassandra-pr-gate/PR-1781 rejected by Butler103 new test failure(s) in 2 builds Found 103 new test failuresShowing only first 15 new test failures
No known test failures found |
The main difference was porting FeatureNeedsIndexRebuildException.