imbajin opened a new pull request, #857: URL: https://github.com/apache/hugegraph-toolchain/pull/857
Editing a `CUSTOMIZE_NUMBER` vertex in Hubble could fail with “Vertex does not exist” even though the same numeric ID was readable from Server. Hubble already resolved the ID using the label's schema, but passed the raw path string to a String-only SDK update overload, which encoded it as a different string ID. Use the existing typed `appendVertexProperty(Vertex)` API when the built vertex has a schema-resolved ID. Both SDK methods perform the same append action. Numeric IDs retain their numeric encoding; numeric-looking `CUSTOMIZE_STRING` IDs remain strings. The existing non-custom fallback remains unchanged; there is no parse-by-appearance or retry against another identity. Validation: - Checkstyle, compilation and 18 focused tests passed. Three new regressions inspect the real SDK PUT path and body for 9000001, Long.MAX_VALUE, string IDs `"9000001"`/`"001"`, and the existing primary-key fallback. The numeric regression fails on master with an unexpectedly quoted ID. - Actual Chromium UI against isolated candidate Hubble (FE3101 → BE8091 with fresh H2 → existing Server/PD/Store), without API mocks or authentication substitution: created only temporary numeric Person 9000001, edited its name through the normal detail drawer, received PUT 200, verified the updated property through the public Server GET, and reopened the UI detail showing the saved value. No browser page errors occurred. - Cleaned only that owned temporary vertex through the visible Gremlin editor using the explicitly scoped `g.V(9000001).drop()`. The public GET then returned 404. Full-record hashes restored the original 3000 vertices and 6000 edges exactly; Person1 and schema were unchanged. The current interface has no standard Server vertex-delete button, so cleanup is not presented as delete-button coverage. No edge CRUD cycle or old identity/pass-through validation matrix is claimed. Before/after screenshots and the detailed verification receipt are retained outside Git and referenced from issue 40 of the [Hubble bug record](https://chatgpt.com/space/page_62cf6a23a284819196000f124fdd6990), available to authorized Page readers. The available tooling cannot upload a persistent public GitHub image attachment; no temporary/raw-branch image links or screenshot assets are added to Git. The final after screenshot shows the reopened numeric ID 9000001 detail with “Hubble typed ID updated” and the save-success notification. Current-head Actions runs remain the source of CI status; the local targeted checks above do not imply that remote CI has finished. Source review: https://github.com/hugegraph/hugegraph-toolchain/pull/102 -- 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]
