[Feature][Connector-V2] Support sink connector for Apache HugeGraph

[Gfreely]

Purpose of this pull request

fix #10001

Does this PR introduce any user-facing change?

This PR introduces a new Sink V2 connector: connector-hugegraph.
This allows users to configure a job to sink data into a HugeGraph database. Users can now write SeaTunnelRow data as either Vertices or Edges, specifying mappings for labels, ID strategy, and properties.

How was this patch tested?

Both Unit Tests (UT) and End-to-End (E2E) Tests were added for this new connector.

Unit Tests:

Added unit tests for HugeGraphSinkConfig to verify the parsing and validation of required sink-side options (e.g., checking necessary fields like url and graph_name).

E2E Tests:

Added a new E2E test module connector-hugegraph-e2e under the seatunnel-e2e/seatunnel-connector-v2-e2t/ directory.

This test uses a Docker container to spin up a temporary HugeGraph service instance.

It runs multiple test cases based on configuration files: testing writing SeaTunnelRow data as vertices, and testing writing SeaTunnelRow data as edges.

This is an example config for vertex synchronization:

env {
  job.mode = "BATCH"
}

source {
  FakeSource {
    plugin_input = "fake_source"
    schema = {
      fields = {
        name = "string"
        age = "int"
      }
    }
  }
}

sink {
  HugeGraph {
    host = "127.0.0.1"
    port = 8080
    graph_name = "hugegraph"
    graph_space = "default"
    selected_fields = ["name", "age"]
    schema_config = {
      type = "VERTEX"
      label = "person"
      idStrategy = PRIMARY_KEY
      idFields = ["name"]
      properties = ["name", "age"]
    }
  }
}

Test Sceenshots:
Use fake source to simulate source database, the detailed configuration is in the documentation.

The following are the query results before and after the sync.

I attempted to sync data from MySQL using stream processing, but I could only synchronize a part of it, likely because I don't have a Hadoop environment.

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config

[davidzollo]

good job
CI failed.
You can check the detailed info through https://github.com/hugegraph/seatunnel/runs/54689699164

[davidzollo]

Please keep the source code in English

[Gfreely]

Thanks. I've addressed all the comments regarding the documentation/notes.

[davidzollo]

I'm not familiar with graphs. Shouldn't this be 2 when knows adds two edges?

[Gfreely]

Apologies for the confusion. This is the expected "edge override" behavior.

To confirm, when an EdgeLabel's frequency is single, attempting to create a second edge with the same source, target, and EdgeLabel will overwrite the existing one.

I have refined the test for this specific scenario and moved it to testEdgeInsert.

[davidzollo]

Good job, things are getting better
I noticed that there're many execptions, I think you can create a unified class HugeGraphConnectorException for HugeGraph，

package org.apache.seatunnel.connectors.seatunnel.hugegraph.exception;

import java.util.Map;
import org.apache.seatunnel.common.exception.SeaTunnelErrorCode;
import org.apache.seatunnel.common.exception.SeaTunnelRuntimeException;

public class HugeGraphConnectorException extends SeaTunnelRuntimeException {
    public HugeGraphConnectorException(SeaTunnelErrorCode code, String msg) { super(code, msg); }
    public HugeGraphConnectorException(SeaTunnelErrorCode code, String msg, Throwable c) { super(code, msg, c); }
    public HugeGraphConnectorException(SeaTunnelErrorCode code, Map<String,String> params) { super(code, params); }
    public HugeGraphConnectorException(SeaTunnelErrorCode code, Map<String,String> params, Throwable c) { super(code, params, c); }
}

[corgy-w]

This document is not needed

[corgy-w]

Could you provide a screenshot of the successful run on your local device

[Gfreely]

Could you provide a screenshot of the successful run on your local device

I have updated the PR with the requested changes. Additionally, I've attached a screenshot verifying that the local database synchronization is successful. Please take a look.

[corgy-w]

Are upsert operations supported now? Does writing graph data need to support upsert?

[Gfreely]

Are upsert operations supported now? Does writing graph data need to support upsert?

The hugegraph-client natively supports upsert operations. For update operations, you can use the update method to update the properties of vertices and edges, excluding the primary key (note that for edges, the values of SortedKeys-related properties constitute the primary key).

[corgy-w]

Are upsert operations supported now? Does writing graph data need to support upsert?

The hugegraph-client natively supports upsert operations. For update operations, you can use the update method to update the properties of vertices and edges, excluding the primary key (note that for edges, the values of SortedKeys-related properties constitute the primary key).

get

[corgy-w]

THX

[davidzollo]

+1
Good job