davidzollo opened a new issue, #10425: URL: https://github.com/apache/seatunnel/issues/10425
Based on the [tracking issue #5677](https://github.com/apache/seatunnel/issues/5677) and source code analysis, the following connectors have not yet implemented true multi-table support (i.e., missing `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: - [ ] **AmazonDynamoDB** (Missing `table_list` option) - [ ] **Cassandra** (Missing `table_list` option) - [ ] **InfluxDB** (Missing `table_list` option) - [ ] **IoTDB** (Missing `table_list` option) - [ ] **MongoDB** (Missing `table_list` option. Note: `cdc-mongodb` supports it, but batch `mongodb` source does not appear to.) - [ ] **Neo4j** (Missing `table_list` option) - [ ] **OpenMLDB** (Missing `table_list` option) - [ ] **Pulsar** (Currently only supports `topic_patterns` for single schema/stream. Needs explicit multi-table support if applicable.) - [ ] **Socket** (Single stream only) - [ ] **TDengine** (Has `sub_tables`, but likely restricted to single Super Table schema. Needs verification if full multi-table support is possible.) - [ ] **Hudi** (Source implementation not found in `seatunnel-connectors-v2/connector-hudi`. Needs to be implemented.) ### Reference - **Feature Issue**: #5677 - **Implementation References**: - `JdbcSource` and `JdbcSourceFactory` (Supports `TABLE_LIST`) - `KafkaSource` (Supports `TABLE_LIST`) - `PaimonSource` (Supports `CatalogOptions.TABLE_LIST`) ### How to contribute 1. Pick a connector from the list. 2. Comment on this issue to claim it. 3. Implement `SupportMultipleTable` logic (usually involves adding `OptionRule` for `TABLE_LIST` and updating the Source to handle multiple `CatalogTable`s). 4. Submit a PR! Thank you! -- 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]
