Gfreely opened a new issue, #10001: URL: https://github.com/apache/seatunnel/issues/10001
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description 1. **Description** HugeGraph is an easy-to-use, efficient, and general-purpose open-source graph database system. To facilitate users in efficiently writing data from various data sources (like MySQL, Kafka, ClickHouse, etc.) into HugeGraph, we propose adding a new V2 connector for SeaTunnel: connector-HugeGraph. 2. **Task Proposal** The implementation of the `HugeGraphSink` connector should support the following core features: **Connection Configuration:** Support configuration for the HugeGraph Server URL, graph name, and authentication details. **Write Vertices (Vertex):** Support mapping and writing `SeaTunnelRow` data as Vertices in HugeGraph, including configuring the `label`, ID strategy (e.g., `PRIMARY_KEY`, `CUSTOMIZE`), and properties. **Write Edges (Edge):** Support mapping and writing `SeaTunnelRow` data as Edges in HugeGraph, including configuring the `label`, `source` vertex ID, `target` vertex ID, and properties. **Batch Writing:** Support efficient batch writes (Batch Write) to improve throughput. For the design document of this connector, please refer to the following repository document: https://github.com/hugegraph/seatunnel/tree/hg-connector ### Usage Scenario _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
