-
Notifications
You must be signed in to change notification settings - Fork 903
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
Task: upgrade RocksDB #4409
Comments
I think we'd better upgrade to 7.10.2 first. Due to 9.2.1 being a major version, we should double-test to see if it breaks the current behaviors. |
+1 for 7.10.2 first |
@dlg99 may I ask the scope of testing to do after the version change in pom file? |
@bhiwagade-rahul with the minor version upgrade the CI should be good enough; maybe a short perf run. I don't remember current state of integration tests for upgrade, I vaguely remember that at some point they weren't executed? |
Main Issue: #4409 ### Motivation Upgrade RocksDB to version 7.10.2 ### Changes Upgrade RocksDB to version 7.10.2
Main Issue: #4409 ### Motivation Upgrade RocksDB to version 7.10.2 ### Changes Upgrade RocksDB to version 7.10.2
Main Issue: apache#4409 ### Motivation Upgrade RocksDB to version 7.10.2 ### Changes Upgrade RocksDB to version 7.10.2
BK currently uses RocksDB 7.9.2.
RocksDB has a bugfix release 7.10.2 (if we decide to to do a minor upgrade for now) and 9.2.1 with variety of performance improvements and features.
We should consider upgrading; I don't know if 9.2.1 would break anything compatibility-wise, 7.10.2 should be safe.
The text was updated successfully, but these errors were encountered: