imbajin commented on code in PR #525:
URL: https://github.com/apache/hugegraph-doc/pull/525#discussion_r4263476495


##########
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}
+
+This proposed feature requires matching [Server 
#3331](https://github.com/apache/hugegraph/pull/3331) and
+[Client/Loader #815](https://github.com/apache/hugegraph-toolchain/pull/815) 
builds. A version label or Docker `latest` tag does not confirm support.
+
+For ordinary imports, the upgraded Loader probes `/mode/owners`. Only a 
route-level unsupported `404` selects the original enum `LOADING`/`NONE` flow.
+That fallback preserves old-Server behavior, including Server 1.7, but 
provides no protection between separate Loader processes.
+Permission, network, invalid-response and acquisition errors do not trigger 
fallback. Graph-source and restore imports keep their existing `RESTORING`
+flow, without the ownership probe or a new automatic reset to `NONE`.
+
+On a supporting Server, each ordinary import retains one 
`instance`/`epoch`/`token` handle. The first owner requires `NONE` and enables 
`LOADING`;
+other Loader processes can join that owned state. One import finishing leaves 
`LOADING` while another owner remains; the last release restores `NONE`.
+Manual `LOADING`, `RESTORING` and `MERGING` are not adopted. Schema changes 
and `--clear-all-data` still need separate coordination.
+
+Use the same direct Server endpoint and authenticated identity for acquisition 
and release. Ownership belongs to that live graph instance;
+it does not coordinate across Servers or isolate ordinary data writes. Release 
the retained handle after its import has stopped.
+Embedded callers must close their Loader with `HugeGraphLoader.shutdown()`.
+
+If release fails, stop the import and retry the REST release with the same 
handle and authenticated identity; shutdown does not promise automatic retry.

Review Comment:
   Addressed in 019fb6e32: documented that the failed handle is output in the 
error message as instance/epoch/token, and linked to the REST section for 
manual release.



-- 
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]

Reply via email to