n24q02m commented on PR #499:
URL: https://github.com/apache/hugegraph-doc/pull/499#issuecomment-6028693420

   ## SeaTunnel 3.0.0 recommendation added (EN + CN guides)
   
   @imbajin Done in f09e8e3:
   
   - **Habits table (bulk-import entry)**: both guides now point graph-to-graph 
data migration at Apache SeaTunnel 3.0.0 (released 2026-09-29), with the 
HugeGraph Loader kept as the alternative for file-based bulk loads.
   - **"Import data" step rewritten** around the recommended direct path 
**Neo4j Source → HugeGraph Sink** (no intermediate file export), noting REST 
for small datasets, plus property → PropertyKey mapping, stable vertex IDs kept 
stable, edge endpoints mapped to existing vertices, and vertices-before-edges 
ordering.
   - **3.0.0 additions called out explicitly** with official links: [Neo4j 
Source](https://seatunnel.apache.org/docs/3.0.0/connectors/source/Neo4j/) 
(`tables_configs` multi-table reads), [HugeGraph 
Sink](https://seatunnel.apache.org/docs/3.0.0/connectors/sink/HugeGraph/) 
(`mappings` refactor + schema-creation behavior), and the new [HugeGraph 
Source](https://seatunnel.apache.org/docs/3.0.0/connectors/source/HugeGraph/) 
for export/migration workflows.
   - **HugeGraph-side setup** links the [Import Graph Data with SeaTunnel Sink 
guide](https://hugegraph.apache.org/docs/quickstart/toolchain/import/hugegraph-seatunnel-connector/)
 from both language versions.
   - Caveat kept explicit: connector capabilities are documented upstream, but 
a complete Neo4j → HugeGraph migration has not been run end-to-end here — 
readers should validate examples on their own data before treating them as 
tested.
   


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