apache/seatunnel

[Umbrella][Feature][Connector] Need help for supporting multi-table source feature

Open

#10425 opened on Jan 31, 2026

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

Description

Based on the tracking issue #5677 and source code analysis, the following connectors have not yet implemented true multi-table support (i.e., missing tables_configs (or deprecated table_list) configuration or the ability to handle multiple distinct tables/schemas in a single source instance).

We need community help to implement these!

Connectors to be implemented:

Type Connector Contributer Status PR
Source AmazonDynamoDB @vbhavh Doing
Source Cassandra @NixonWahome Doing #10896
Source Elasticsearch @FuYouJ Doing
Source Hudi @LiJie20190102 Doing
Source InfluxDB Todo
Source IoTDB Todo
Source MongoDB (Batch) @chl-wxp Doing
Source Neo4j Todo
Source OpenMldb Todo
Source Pulsar @onceMisery Done #10825
Source RabbitMQ @Anthippi Doing #10557
Source Redis @JeremyXin Done #10601
Source RocketMQ @kuleat Done #10619

Reference

  • Feature Issue: #5677
  • Implementation References:
    • JdbcSource and JdbcSourceFactory (Supports TABLE_LIST - Note: newer implementations should refer to TABLE_CONFIGS)
    • KafkaSource (Supports TABLE_LIST)
    • PaimonSource (Supports CatalogOptions.TABLE_LIST)
    • Standard: Please use ConnectorCommonOptions.TABLE_CONFIGS (tables_configs) as the configuration key, as CatalogOptions.TABLE_LIST (table_list) is deprecated.

How to contribute

  1. Pick a connector from the list.
  2. Search Pull Requests to ensure no one is already working on it (keywords: "multi table", "ConnectorName").
  3. Comment on this issue to state which connector you'd like to help implement.
  4. Implement SupportMultipleTable logic (usually involves adding OptionRule for TABLE_CONFIGS and updating the Source to handle multiple CatalogTables).
  5. Submit a PR!

Contributor guide

Tech stack
java
Domain
databackend
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.
1-2 days
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
JavaSeaTunnel architecture basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
This is an umbrella issue. To contribute, pick one connector from the list that is marked 'Todo' or has no active PR. Review the tracking issue #5677 and study existing implementations like JdbcSource (which uses TABLE LIST) and the newer standard using ConnectorCommonOptions.TABLE CONFIGS. Check linked PRs for examples (e.g., PR #10825 for Pulsar). Ensure no one else is working on the connector by searching pull requests. Then implement the SupportMultipleTable interface, update the source to handle multiple CatalogTables, and add the appropriate OptionRule. Comment on this issue to claim the connector.