apache/seatunnel

[Umbrella][Feature][Connector] Implement multi-table sink support for connectors

Open

#10426 opened on Jan 31, 2026

View on GitHub
 (20 comments) (0 reactions) (0 assignees)Java (6,897 stars) (1,432 forks)batch import
featuregood first issuehelp wanted

Description

Description

Based on the tracking issue #5652 and codebase analysis, many sink connectors still lack support for the SupportMultiTableSink interface. We are looking for contributors to help implement this feature for the remaining connectors.

Implementing SupportMultiTableSink allows the connector to handle multiple tables in a single sink instance, which is crucial for database synchronization scenarios (e.g., CDC).

Connectors to be implemented

Type Connector Contributer Status PR
Sink AmazonDynamodb @Best2Two Done #10497
Sink Cassandra Todo
Sink DingTalk Todo
Sink Feishu Todo
Sink GoogleFirestore Todo
Sink IoTDB Todo
Sink Neo4j Todo
Sink Pulsar @Muktha9491 Doing #10558, #10670
Sink RabbitMQ Todo
Sink Rocketmq @onceMisery Doing
Sink S3Redshift Todo
Sink SelectDBCloud Todo
Sink Sentry Todo
Sink Slack Todo
Sink Socket Todo
Sink Tablestore Todo
Sink Kafka @misi1987107 Doing #10154

How to Contribute

  1. Pick a connector: Choose one from the list above.
  2. Claim the task: Comment on this issue (e.g., "I would like to work on AmazonDynamodb").
  3. Implement:
    • Modify the Sink class to implement the org.apache.seatunnel.api.sink.SupportMultiTableSink interface.
    • Update the SinkFactory to handle CatalogTables correctly.
    • Ensure tables_configs or equivalent logic is handled if necessary (though Sink usually relies on the upstream CatalogTable).
  4. Reference:
    • You can refer to the implementation of JdbcSink or ElasticsearchSink.
  5. Submit PR: Submit a Pull Request and link it to this issue.

Thank you for your contribution! Please leave a message if you‘d like to implement the multi - table sink feature for any connector.

Contributor guide

Tech stack
java
Domain
backenddata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java knowledgeUnderstanding of sink APIFamiliarity with chosen connector
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
First, read the tracking issue #5652 and the existing implementations of JdbcSink and ElasticsearchSink. Then choose a connector from the 'Todo' list. Examine the current sink class and factory for that connector. Implement the SupportMultiTableSink interface by following the pattern in JdbcSink. Ensure CatalogTable handling is correct. Submit a PR linking to this issue.