Muktha9491 opened a new pull request, #10558:
URL: https://github.com/apache/seatunnel/pull/10558
### Purpose of this pull request
This PR adds multi-table sink support for the Pulsar connector.
The Pulsar sink can now route records dynamically to different Pulsar topics
based on `SeaTunnelRow.getTableId()`. Each topic maintains a dedicated
Pulsar producer stored in a producer map, allowing the connector to support
multiple tables in a single pipeline.
This change implements `SupportMultiTableSink` for the Pulsar connector.
Closes #10426
### Does this PR introduce any user-facing change?
Yes.
Previously, the Pulsar sink only supported writing records to a single topic.
With this change, the connector supports multi-table pipelines by routing
records to different Pulsar topics using `SeaTunnelRow.getTableId()`.
### How was this patch tested?
The change was tested locally by building the connector module and verifying
the multi-table routing logic.
Steps performed:
1. `mvn clean install`
2. `mvn spotless:check`
3. Verified successful compilation and connector-pulsar module tests.
The routing behavior was reviewed to ensure records are written to different
Pulsar topics based on `SeaTunnelRow.getTableId()`.
No additional unit tests were added because the change only affects routing
logic and existing Pulsar sink functionality remains unchanged.
### Check list
* [ ] If any new Jar binary package adding in your PR, please add License
Notice
* [ ] If necessary, please update the documentation
* [ ] If necessary, please update `incompatible-changes.md`
* [ ] If you are contributing the connector code, please check that required
connector configuration files are updated (not applicable for this
change)
--
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]
