Gfreely opened a new pull request, #10002:
URL: https://github.com/apache/seatunnel/pull/10002

   <!--
   
   Thank you for contributing to SeaTunnel! Please make sure that your code 
changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   ## Contribution Checklist
     - Make sure that the pull request corresponds to a [GITHUB 
issue](https://github.com/apache/seatunnel/issues).
     - Name the pull request in the form "[Feature] [component] Title of the 
pull request", where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
     - Minor fixes should be named following this pattern: `[hotfix] [docs] Fix 
typo in README.md doc`.
   -->
   
   ### 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.
   
   
   ### Check list
   
   * [x] If any new Jar binary package adding in your PR, please add License 
Notice according
     [New License 
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/contribution/new-license.md)
   * [x] If necessary, please update the documentation to describe the new 
feature. https://github.com/apache/seatunnel/tree/dev/docs
   * [x] If you are contributing the connector code, please check that the 
following files are updated:
     1. Update 
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
 and add new connector information in it
     2. Update the pom file of 
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
     3. Add ci label in 
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
     4. Add e2e testcase in 
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
     5. Update connector 
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)


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

Reply via email to