imbajin opened a new pull request, #808:
URL: https://github.com/apache/hugegraph-toolchain/pull/808

   Loader expanded a valid `@loader.args` file and then rejected it because the 
original process argument count was below three. It now relies on the required 
mapping option and existing validators, accepting response files and minimal 
commands using defaults while invalid inputs still fail.
   
   Separate-process regressions cover response files, spaced filenames, default 
options and invalid inputs. The Loader README explains file syntax, relative 
paths, credential-file permissions and writable progress directories.
   
   Validation: the final source and bytecode passed a real native RocksDB 
before/after probe through the unchanged launcher. The old single-file call 
returned usage without importing; the fixed call imported two vertices and one 
edge, with exact Chinese properties and endpoints read back independently. 
Expanded arguments produced equivalent data and schema. Final-head parser 
tests, formatting and Checkstyle passed; three independent reviews found no 
material issue. The original Kubernetes Job and large workloads remain separate 
acceptance scopes.
   
   The same source branch passed the org checks, including Loader/Hubble 
validation against the configured candidate and release 1.7, image builds, 
Spark/CDC compatibility, module summary, CodeQL and coverage. [Org validation 
#61](https://github.com/hugegraph/hugegraph-toolchain/pull/61).
   
   Documentation: Loader README updated. Paired website guides are in [org 
documentation #44](https://github.com/hugegraph/hugegraph-doc/pull/44); its 
current-head CI must pass before the same branch is submitted to ASF. 
Coordinate code and website documentation merges.
   


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