Join GitHub today
Consolidate rocksdb imports into one module for engine abstraction #4229
This is a single step in abstracting the engine API.
Right now rocksdb imports are spread out across the project. If there's ever to be an abstract engine API, then those imports will need to be replaced with abstract ones. And that effort will be simpler if all the rocksdb imports come from the same module.
So this issue is to remove all the imports from the rocksdb crate and replace them with imports from
As per previous comment, the steps to do this are something like:
To me, not knowing much about the engine, I would think the first step is to centralize all calls to the rocksdb crate into one place within tikv, so the entire engine API surface is known and has a single module from which to pull out an abstract interface.
I think the place those calls should be directed to is
Help wanted. I can mentor, or possibly @huachaohuang.
referenced this issue
Feb 19, 2019
Also, I just noticed that someone else already volunteered for this issue. Sorry about that