feat(rocksdb): Remove all calls of Pegasus introduced APIs on RocksDB #556
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Use official RocksdDB
What is changed and how it works?
Check List
Tests
Test compatibility with 2.0.0:
Code changes
No
No
No
Yes.
Meta data (Pegasus data version, last manual compact finish timestamp, dcree) will NOT write to RocksDB's manifest anymore.
Side effects
No
No
Upgrade:
1.x -> this version: forbidden (server will core)
2.0 -> this version: compatible
Downgrade:
this version -> 1.x: forbidden (server will run with error, table can not be healthy, cause 1.x can't open RocksDB with multi-CFs)
this version -> 2.0: partial compatible, and config
[pegasus.server].get_meta_store_type
should bemetacf
in order to read meta data from meta CF.Related changes
Yes
Yes
Yes