junjunclub commented on issue #10681: URL: https://github.com/apache/seatunnel/issues/10681#issuecomment-5772148092
@SEZ9 @DanielLeens @goutamadwant Quick update on the current Layer 1 (`--dry-run connect`) connector support status. ### 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 * Cassandra Source — #12430 (draft; depends on #12429) * Redis Source / Sink — #12431 (draft) * RabbitMQ Source — #12432 * Neo4j Source — #12433 The connector-specific implementations above reuse the existing Layer 1 validation SPI without changes to `DryRunConnectValidator` or the shared validation interfaces. ### Proposed / no active implementation PR * MySQL CDC Source + Elasticsearch Sink — #12357 Other Source/Sink connectors are still reported as `SKIPPED` unless they implement: * `SupportSourceDryRunValidation` * `SupportSinkDryRunValidation` Recent additions: * Cassandra Source (#12430) * Redis Source / Sink (#12431) * RabbitMQ Source (#12432) * Neo4j Source (#12433) -- 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]
