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


##########
content/en/docs/language/migrate-from-neo4j.md:
##########
@@ -0,0 +1,113 @@
+---
+title: "Migrating from Neo4j"
+linkTitle: "Migrating from Neo4j"
+weight: 4
+---
+
+### Who this page is for
+
+Neo4j users evaluating HugeGraph. HugeGraph's Cypher coverage is defined by
+the [`cypher-for-gremlin`](https://github.com/opencypher/cypher-for-gremlin)
+translator and is not 1:1 with Neo4j — see
+[Known limitations](/docs/language/hugegraph-cypher/#known-limitations) for 
what
+released HugeGraph versions do, and the
+[Cypher compatibility notes](/docs/language/cypher-compatibility/) for the
+development-tree verification record and
+[HugeGraph Cypher](/docs/language/hugegraph-cypher/) for usage.
+
+### What carries over directly
+
+| Neo4j concept | HugeGraph equivalent |
+|---|---|
+| Property graph model (nodes / relationships / properties) | Same — vertex 
labels / edge labels / properties |
+| Core Cypher: `MATCH`/`WHERE`/`RETURN`/`CREATE`/`SET`/`DELETE` | Works as-is 
(REST `/cypher` endpoint or Java client `CypherManager`), subject to the schema 
and index rules below |
+| Simple aggregations (`count`/`sum`/`min`/`max`/`avg`) | Works as-is |
+| Traversal-heavy queries | Gremlin traversals or the [traverser REST 
APIs](/docs/clients/restful-api/traverser/) (k-out, shortest path, 
personalrank, ...) |
+
+### Habits you need to change
+
+| In Neo4j | In HugeGraph |
+|---|---|
+| `CREATE INDEX` / `CREATE CONSTRAINT` | Create property indexes through the 
[IndexLabel REST API](/docs/clients/restful-api/indexlabel/); uniqueness 
constraints map to `UNIQUE` IndexLabels (which reject duplicates with a 
conflict error). Node keys map to non-nullable keys plus a composite `UNIQUE` 
index; a `UNIQUE` index cannot include all primary keys of a `PRIMARY_KEY` 
label (the server rejects it), so to keep duplicate rejection use 
`CUSTOMIZE_STRING` keyed on the Neo4j node id with a `UNIQUE` index on the 
business key. Property existence constraints map to non-nullable keys on 
[VertexLabels](/docs/clients/restful-api/vertexlabel/) or 
[EdgeLabels](/docs/clients/restful-api/edgelabel/). Note that `primary_keys` 
defines vertex identity rather than a constraint—a duplicate `CREATE` 
overwrites instead of failing |
+| Implicit schema (add properties freely) | **Strong schema**: define 
VertexLabel / EdgeLabel / PropertyKey before writing data |
+| Property predicates in `WHERE` need no index | The starting vertex lookup in 
`WHERE` needs a covering index unless it is an equality on every primary key of 
the label: create a `SECONDARY` or `RANGE` IndexLabel first, and use `RANGE` 
for comparisons such as `>` or `<`. Without a covering index the request 
returns `status.code` 400 with a "not indexed" error |
+| Parameterized queries `$param` | Released versions send the raw statement 
only — a missing binding is inlined as `null` instead of failing (a predicate 
on it matches no rows, and a write does not reliably store `null`: `SET` 
removes the property, `CREATE` can store the marker string `"  cypher.null"` or 
fail), so validate values client-side; JSON-bound parameters are available on 
`master` after [ASF PR #3289](https://github.com/apache/hugegraph/pull/3289), 
with a fixed limit of 16 top-level bindings |
+| `CALL dbms.*` / `CALL algo.*` procedures | Equivalent capabilities live in 
the [traverser](/docs/clients/restful-api/traverser/), 
[task](/docs/clients/restful-api/task/), and other REST APIs |
+| Driver: Neo4j Bolt driver | 
[hugegraph-client](/docs/clients/hugegraph-client/) (`CypherManager`) or any 
HTTP client |
+| Transaction boundaries inside a Cypher statement | One statement per 
request; graph-to-graph data migration uses [Apache SeaTunnel 
3.0.0](https://seatunnel.apache.org/download/) (preferred — see below), 
file-based bulk loads use the [HugeGraph 
Loader](/docs/quickstart/toolchain/hugegraph-loader/) |
+
+The latest published release is 1.7.0 as of 2026-10-09; the merged JSON-bound 
request form is a
+`master` feature, not a promise about that release. See the compatibility 
notes for its validated contract.
+
+### Suggested migration path
+
+1. **Inventory your queries**: classify the Cypher in your application against
+   the [Known limitations](/docs/language/hugegraph-cypher/#known-limitations)
+   (which describe released behaviour) into
+   "works as-is / rewrite as Gremlin / switch to a REST API"; the
+   [compatibility notes](/docs/language/cypher-compatibility/) record only the
+   development-tree contract.
+2. **Create the schema first**: define VertexLabel / EdgeLabel / PropertyKey
+   and indexes through the schema API — HugeGraph requires the schema to
+   exist before data is written.
+3. **Import data**: the preferred path is
+   [Apache SeaTunnel 3.0.0](https://seatunnel.apache.org/download/) (released
+   2026-09-29) running **Neo4j Source → HugeGraph Sink** directly — no
+   intermediate file export. REST remains fine for small datasets; the
+   [HugeGraph 
Loader](https://github.com/apache/hugegraph-toolchain/tree/master/hugegraph-loader)
+   stays an alternative for file-based imports. HugeGraph-side setup
+   (environment, `mappings`, vertex/edge import examples) is covered in the
+   [Import Graph Data with SeaTunnel Sink 
guide](/docs/quickstart/toolchain/import/hugegraph-seatunnel-connector/).
+
+   The [SeaTunnel 3.0.0 connector 
docs](https://seatunnel.apache.org/docs/3.0.0/introduction/about/) document
+   what to rely on:
+   - [Neo4j 
Source](https://seatunnel.apache.org/docs/3.0.0/connectors/source/Neo4j/) reads 
Cypher
+     query results with explicit field schemas; 3.0.0 adds multi-table reads 
via `tables_configs`.
+   - [HugeGraph 
Sink](https://seatunnel.apache.org/docs/3.0.0/connectors/sink/HugeGraph/) is
+     refactored in 3.0.0 with multi-mapping support — use the recommended 
`mappings` configuration
+     for vertices/edges and follow its schema-creation behavior. Note that the 
Sink defaults
+     `batch_failure_fallback=true`, which logs and skips failed records and 
only fails after 500 skips

Review Comment:
   ⚠️ The released connector source sets `batch_failure_fallback` to `false` 
and `max_insert_errors` to `0`, so an omitted configuration fails fast rather 
than skipping 500 records. [HugeGraphOptions.java at the v3.0.0 
tag](https://github.com/apache/seatunnel/blob/5056e3e1766690a2fa01934b9349c645d8086b93/seatunnel-connectors-v2/connector-hugegraph/src/main/java/org/apache/seatunnel/connectors/seatunnel/hugegraph/config/HugeGraphOptions.java#L89-L109)
 defines both defaults. Please correct this description in both languages and 
describe skipping as opt-in. This also corrects the defaults stated in the 
earlier review comment.



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