apache / apache/hugegraph-toolchain

[Feature] Hubble new feature summary V2 (Wanted)

Open
#651 0 comments 4 reactions 0 assignees View on GitHub
enhancement hubble
Dominant language
Java
Stars
121
Forks
125
Avg merge
10d 10h
Merged PRs (30d)
3

Description

### Search before asking

- [x] I had searched in the [feature](https://github.com/apache/incubator-hugegraph-toolchain/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement.

### Feature Description (功能描述)
The V2 version mainly updates the following features:
- Support for access authentication and user role management.
- Support for OLAP and OLTP graph algorithm analysis.
- A brand new control panel UI.
- Optimized user experience.

### Remain Work (剩余工作)
Currently, most of the corresponding functions have been implemented and tested, but the following work still need to be completed ( some of them are partly done):
- [x] Complete the functionality transferring and testing.
- [ ] Complete compatibility work with [PR #633](https://github.com/apache/incubator-hugegraph-toolchain/pull/633). **←IMPORTANT and currently working on**
- [ ] Complete user testing for the new environment's build & use.
- [ ] Fix a few known bugs.
- [ ] Clean code and dependency
- [ ] Complete the usage documentation [PR #373](https://github.com/apache/incubator-hugegraph-doc/pull/373)
- [ ] Complete the preparations before the release, including:
- - [x] Setting ASF header information.
- - [ ] Dependency review.
- [ ] Support i18n and complete the corresponding translation work.

### Are you willing to submit a PR?

- [x] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the compatibility work in PR #633 and the usage documentation in PR #373, then assess the remaining checklist items for user testing, known bugs, dependencies, release preparation, and i18n. Done means the V2 feature set is compatible, tested in the new environment, documented, cleaned up, translated, and ready for release.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.