-
Notifications
You must be signed in to change notification settings - Fork 521
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
chore: rollback cassandra to 3.11.16 #2374
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2374 +/- ##
=============================================
+ Coverage 53.81% 66.26% +12.44%
- Complexity 545 830 +285
=============================================
Files 509 509
Lines 42139 42139
Branches 5836 5836
=============================================
+ Hits 22679 27922 +5243
+ Misses 17027 11459 -5568
- Partials 2433 2758 +325 ☔ View full report in Codecov by Sentry. |
incubator-hugegraph/hugegraph-server/hugegraph-dist/docker/example/docker-compose-cassandra.yml Line 42 in 062bb3d
There is a related file here, we use cassandra:4 in docker-compose. If we rollback cassandra, maybe we should change the version here. |
thanks for the reminder,seems we do need it |
thank you! I will fix it |
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.
Purpose of the PR
This pull request reverts the changes introduced in PR #2300 , which upgraded Cassandra from version 3.11.12 to 4.0.10. The upgrade caused compatibility issues that were not anticipated, and as a result, we are reverting back to 3.11.16 version to maintain stability and functionality.
Main Changes
Note Regarding 3rd Party Error
Users experiencing the error reported by 3rd party (GHSA-m9p2-j4hg-g373) should note that we have upgraded to Cassandra version 3.11.16.
This issue may be related to Cassandra 3, and any resolution might be addressed when upgrading to Cassandra 4. As this is not within our control, we recommend monitoring Cassandra updates for a potential fix.
Verifying these changes
Does this PR potentially affect the following parts?
Documentation Status
Doc - TODO
Doc - Done
Doc - No Need