WaterWhisperer opened a new pull request, #3024:
URL: https://github.com/apache/hugegraph/pull/3024
<!--
Thank you very much for contributing to Apache HugeGraph, we are happy
that you want to help us improve it!
Here are some tips for you:
1. If this is your first time, please read the [contributing
guidelines](https://github.com/apache/hugegraph/blob/master/CONTRIBUTING.md)
2. If a PR fix/close an issue, type the message "close xxx" (xxx is the
link of related
issue) in the content, GitHub will auto link it (Required)
3. Name the PR title in "Google Commit Format", start with "feat | fix |
perf | refactor | doc | chore",
such like: "feat(core): support the PageRank algorithm" or "fix: wrong
break in the compute loop" (module is optional)
skip it if you are unsure about which is the best component.
4. One PR address one issue, better not to mix up multiple issues.
5. Put an `x` in the `[ ]` to mark the item as CHECKED. `[x]` (or click
it directly after
published)
-->
## Purpose of the PR
Add ToplingDB support as an optional RocksDB-compatible storage path.
This PR rebases and prepares the existing ToplingDB adaptation work for
review on the current `master`. ToplingDB is integrated as an optional provider
for RocksDB-based storage, allowing users to enable RocksDB/ToplingDB
configuration and the ToplingDB Web UI while preserving the standard RocksDB
path.
<!--
Please explain more context in this section, clarify why the changes are
needed.
e.g:
- If you propose a new API, clarify the use case for a new API.
- If you fix a bug, you can clarify why it is a bug, and should be
associated with an issue.
-->
## Main Changes
<!-- Please clarify what changes you are proposing. The purpose of this
section is to outline the changes and how this PR fixes the issue. These change
logs are helpful for better and faster reviews.)
For example:
- If you introduce a new feature, please show detailed design here or add
the link of design documentation.
- If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
- If there is a discussion in the mailing list, please add the link. -->
- Add `hugegraph-rocksdb-provider` module
- Update HugeGraph Server RocksDB integration
- Add ToplingDB preload support in server dist
- Add PD / Store ToplingDB integration
- Add Maven / CI / dependency metadata updates
- Add ToplingDB docs and specs
## Verifying these changes
<!-- Please pick the proper options below -->
- [ ] Trivial rework / code cleanup without any test coverage. (No Need)
- [ ] Already covered by existing tests, such as *(please modify tests
here)*.
- [x] Need tests and can be verified as follows:
- Built packaged dist artifacts for Server / PD / Store
- Verified packaged `rocksdbjni-8.10.2-SNAPSHOT.jar` contains ToplingDB
resources including `org/rocksdb/ SidePluginRepo.class`
- Ran Server with ToplingDB enabled
- Ran Server without `rocksdb.option_path`
- Ran PD / Store with ToplingDB config
## Does this PR potentially affect the following parts?
<!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
- [x] Dependencies ([add/update
license](https://hugegraph.apache.org/docs/contribution-guidelines/contribute/#321-check-licenses)
info &
[regenerate_known_dependencies.sh](../install-dist/scripts/dependency/regenerate_known_dependencies.sh))
<!-- Don't forget to add/update the info in "LICENSE" & "NOTICE" files (both
in root & dist module) -->
- [x] Modify configurations
- [ ] The public API
- [x] Other affects (typed here)
- Adds native library preload logic for ToplingDB-enabled RocksDB JNI
runtime.
- Adds optional ToplingDB Web UI support.
- Adds RocksDB provider SPI and routes RocksDB opening through the
provider loader.
- [ ] Nope
## Documentation Status
<!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
- [ ] `Doc - TODO` <!-- Your PR changes impact docs and you will update
later -->
- [x] `Doc - Done` <!-- Related docs have been already added or updated -->
- [ ] `Doc - No Need` <!-- Your PR changes don't impact/need docs -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
