junjunclub commented on issue #10681: URL: https://github.com/apache/seatunnel/issues/10681#issuecomment-5755283272
Thanks. I'll keep the Layer 1 connector support status tracked here. ### Layer 1 (`--dry-run connect`) connector support #### Merged * JDBC Source / Sink — #11186 * FakeSource — #11186 * Kafka Source — #12167 * S3File Source — #12242 Kafka Source and S3File Source currently provide scoped validation rather than complete runtime-equivalent validation: * Kafka Source validates broker authentication, topic metadata, and runtime output schema, but does not prove consumer/group permissions or successful message deserialization. * S3File Source performs metadata-level connectivity validation for its currently supported configuration scope and does not validate object contents or every S3/IAM scenario. #### In progress * MongoDB Source — #12399 * Kafka Sink — #12400 #### Proposed / no active merged implementation * MySQL CDC Source + Elasticsearch Sink — #12357 Other Source/Sink connectors are still reported as `SKIPPED` unless they implement: * `SupportSourceDryRunValidation` * `SupportSinkDryRunValidation` I'd like to pick up **Redis Source and Sink** next, unless someone is already working on them. The initial scope would be: * reuse the existing Layer 1 SPI without changing `DryRunConnectValidator` or the shared interfaces; * validate Redis connectivity and authentication for both single-node and cluster modes; * avoid reading keys or writing data during validation; * reuse configured schema / `table_configs` for source schema inference rather than inspecting Redis values; * keep connection attempts bounded and close clients/resources reliably; * add focused tests and update the EN/ZH connector documentation. I'll link the PR back to this issue once it's ready. -- 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]
