We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I am reading at https://docs.nebula-graph.com.cn/3.2.0/1.introduction/3.nebula-graph-architecture/4.storage-service/,
it says Nabula Graph is using 自研 KV store.
自研
Somewhere, I heared that Nebula Graph is using HBase or RocksDB, so I want to ask for a clarification, thanks!
The text was updated successfully, but these errors were encountered:
Hi, I am reading at https://docs.nebula-graph.com.cn/3.2.0/1.introduction/3.nebula-graph-architecture/4.storage-service/, it says Nabula Graph is using 自研 KV store. Somewhere, I heared that Nebula Graph is using HBase or RocksDB, so I want to ask for a clarification, thanks!
NebulaGraph Storage is an in-house thing based on RocksDB, where the raft layer and meta are all created from scratch :).
https://github.com/vesoft-inc/nebula/tree/master/src/storage
PS. Years before we used to support both HBase and RocksDB, then we decided to drop HBase support at some time years ago.
Sorry, something went wrong.
NebulaGraph Storage is an in-house thing based on RocksDB, where the raft layer and meta are all created from scratch :). https://github.com/vesoft-inc/nebula/tree/master/src/storage PS. Years before we used to support both HBase and RocksDB, then we decided to drop HBase support at some time years ago.
Thanks @wey-gu for the clarification!
No branches or pull requests
Hi,
I am reading at https://docs.nebula-graph.com.cn/3.2.0/1.introduction/3.nebula-graph-architecture/4.storage-service/,
it says Nabula Graph is using
自研
KV store.Somewhere, I heared that Nebula Graph is using HBase or RocksDB, so I want to ask for a clarification, thanks!
The text was updated successfully, but these errors were encountered: