SebastianGruza commented on issue #748: URL: https://github.com/apache/hugegraph-toolchain/issues/748#issuecomment-5751544513
I'd like to take the two checklist items everything else hangs on: **the compatibility matrix with shared fixtures** and **the baseline benchmark of the current implementation**. Without them no Rust client or loader has a reference point, and the roadmap itself asks for "differential, cross-language parity" and "reproducible benchmarks" before implementation. Both are needed regardless of Rust: the Go client covers a fraction of the Java client's surface today and nothing measures that. Where I come from: recently #771 (DECIMAL in the client, loader, spark connector and Hubble, E2E against a server built from apache/hugegraph#3209), on the server side apache/hugegraph#3220, apache/hugegraph#3221 and the Helm chart (hugegraph/hugegraph#221), always with a reproduction and tests on my own cluster. I am not declaring a Rust client; I am declaring the foundation that lets someone write one and prove parity, and if the fixtures turn out stable along the way I can add a minimal vertical slice (transport + `/versions`) as proof in a third language. Child issue with scope, non-goals and acceptance criteria: #772. I'll open the first small PR this week: the fixture format plus a runner for the Java client on a dozen endpoints. If you prefer a different layout or a different first step, correct me in the child issue; until then I build on what is in the repo. -- 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]
