apache/hugegraph

1.8.0 release checklist Focus: Hubble, ordinary Loader and Client. Mainline + matching immutable RCs: Server/Toolchain/Doc master; AI main. Java 17 Server/Toolchain foundations are delivered. Latest changes checked 2026-10-09 20:26–20:30 UTC; CI evidence is SHA-bound and time-limited below. 1.7 → 1.8 upgrade compatibility remains a release gate. Outstanding Server / PD / Store P0 · HStore upgrade #3224 · fix or verified migration/recovery; preserve old 0xFFFE data through startup replay, first write and rollback on every replica P1 · Index coverage #3243 · query/index + RC regressions open P1 · Query wrappers #2994 · conflicts + current-head review closure P1 · Mounted auth upgrades #3192 · conflicts + YAML/image/config acceptance P1 · External runtime paths #3253 · conflicts; PD/Store -jar ordering + path/cron regressions; CI approval P1 · Cypher error contract #3241 · conflicts; coordinate compatible follow-up P1 · Cypher compatibility #3259 · draft/confli

Goal Explore an incremental Rust implementation for selected HugeGraph Server, HStore, and PD components, especially performance- or memory-sensitive paths where Rust can provide measurable safety and efficiency benefits. This is a parent tracking issue, not a commitment to rewrite the whole server. The current implementation remains the compatibility baseline, and Java/Rust components may coexist behind stable process, protocol, or storage boundaries. Roadmap at a glance Toolchain foundations │ v ┌─ This repository ─────────────────┐ │ Server core -> HStore -> PD │ └───────────────────────────────────┘ │ v Computer kernels -> Vermeer/OLAP Each arrow is a review gate, not an automatic rewrite. Proposed priority Server core Begin with bounded leaf components, memory management, codecs, or performance-sensitive data structures

Problem PR #3008 exposed 22 historically excluded HStore core-test cases after the Maven backend property was propagated to every Surefire execution. Scoping that property back to the API-test execution fixes the PR regression, but it does not resolve the underlying HStore defects or the legacy test guards. The exclusions were introduced by d36e05ece8554fee73ba332147560930b3eba234 as temporary HStore skips. Their conditions use Assume.assumeTrue(isHstore) despite saying skip this test for hstore. Before PR #3008, the core-test JVM did not receive the backend property, so these tests were skipped because the value was null. A global property exposed 21 failures/errors and reduced skipped tests from 42 to 20. Historical evidence: Passing baseline: https://github.com/apache/hugegraph/actions/runs/29094884977 First exposing run: https://github.com/apache/hugegraph/actions/runs/29097183435 Latest repeated failure: https://github.com/apache/hugegraph/actions/runs/29105710720 Confirmed tech

Feature Description (功能描述) Currently, the REST API responses in the server,pd and store modules lack a standardized format. When a request fails (e.g., Raft group not found, store heartbeat timeout), the error message is often missing or buried in logs rather than being returned in a clear, actionable format to the user. An example response format is as follows { "code": 200, "message": "success", // hint for user "data": { ... }, "status": "OK" }