imbajin commented on code in PR #525:
URL: https://github.com/apache/hugegraph-doc/pull/525#discussion_r4255314491
##########
content/en/docs/quickstart/toolchain/hugegraph-loader.md:
##########
@@ -986,6 +990,29 @@ bin/hugegraph-loader.sh \
Expected result: two vertices and zero edges imported. This example uses
dedicated schema names to avoid conflicts with a preloaded `person` label. In
Hubble, run `g.V().hasLabel('docs_smoke_person').values('docs_name')` to
confirm `docs-smoke-alice` and `docs-smoke-bob`.
+#### 3.4.6 Concurrent imports and LOADING ownership {#loading-ownership}
+
+Upgrade both Server and Client/Loader to builds containing `/mode/owners`
protocol 1; a version number or Docker `latest` tag alone does not confirm
support.
+Server 1.7 recognizes `LOADING` but has no ownership endpoint. Normal imports
fail if the capability is absent or invalid, without falling back to enum
+mode PUT or `NONE`. This check precedes `--clear-all-data`, Schema creation
and import-data writes; `--create-graph` can create the target graph first.
Review Comment:
Fixed in the current head. Both EN/ZH Loader and GraphMode pages now label
this contract as proposed and unreleased, state that released packages, earlier
1.8 builds and current Apache master lack it, and explain that the generic
download/master-build instructions do not select the required PR builds. The
Loader sections link both paired draft implementations (apache/hugegraph#3331
and apache/hugegraph-toolchain#815) and pin their reviewed source refs. Hubble
#814 alone does not supply the owner-aware Client/Loader.
The same update documents the protocol check before RESTORING, followed by
successful-PUT-only cleanup after worker drain. Repository link checks, a
strict Hugo 0.165 Extended build, bilingual rendered-page readbacks and an
independent documentation review passed. Both organization and ASF PRs now
expose the same published source; current-head CI and coordinated merges remain
open.
--
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]
