goutamadwant opened a new pull request, #11865:
URL: https://github.com/apache/seatunnel/pull/11865
<!--
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
Part of #9813.
This adds the first scoped NebulaGraph connector slice as a vertex sink:
- Uses the official NebulaGraph Java `SessionPool` client for an existing
space and tag.
- Supports batched `INSERT` and `UPDATE` vertex writes.
- Validates graphd addresses, identifiers, vertex IDs, write fields, and
supported data types before writing.
- Keeps property values parameterized and escapes string vertex IDs before
building nGQL.
- Registers the connector in the distribution and plugin mappings.
- Adds English and Chinese documentation, dependency license entries, unit
tests, and a NebulaGraph 3.8 E2E test.
Source reads, edge writes, schema creation, and delete handling are
intentionally left for follow-up work.
### Does this PR introduce _any_ user-facing change?
Yes. Users can configure a `NebulaGraph` sink to write SeaTunnel rows as
vertices to an existing NebulaGraph 3.5 or later space and tag.
The sink provides at-least-once delivery. `INSERT` uses `INSERT VERTEX IF
NOT EXISTS`; `UPDATE` updates existing vertices. `DELETE` rows are rejected.
### How was this patch tested?
Added unit coverage for configuration validation, host parsing, statement
construction, vertex ID escaping, batching, checkpoint flushes, changelog
handling, unsupported types, and failed-write close behavior.
Added an E2E test that runs SeaTunnel jobs against NebulaGraph 3.8 and
verifies both insert and update results. I also verified single-row and two-row
batched updates against a local NebulaGraph 3.8 cluster through the same
`SessionPool` client path.
Verified with:
```shell
./mvnw -pl seatunnel-connectors-v2/connector-nebulagraph clean package
./mvnw -pl
seatunnel-connectors-v2/connector-nebulagraph,seatunnel-e2e/seatunnel-connector-v2-e2e/connector-nebulagraph-e2e
-DskipTests -DskipITs test-compile
```
### 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/developer/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 necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR. Not applicable because this adds a new
connector without changing an existing contract.
* [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]
