DanielCarter-stack commented on issue #10394: URL: https://github.com/apache/seatunnel/issues/10394#issuecomment-3797719202
<!-- code-pr-reviewer --> Thanks for the feature request. I've verified that SeaTunnel currently does not have dedicated connectors for GCS, BigQuery, or AlloyDB. **Current state:** - **GCS**: No `connector-file-gcs` module exists (only S3/OSS/COS/OBS/Hadoop are supported in `seatunnel-connectors-v2/connector-file/`) - **BigQuery**: No dedicated connector; not in `DatabaseIdentifier.java` (`seatunnel-connectors-v2/connector-jdbc/src/main/java/org/apache/seatunnel/connectors/seatunnel/jdbc/internal/dialect/`) - **AlloyDB**: No AlloyDB dialect or documentation (PostgreSQL-compatible, so JDBC connector may work with PostgreSQL driver) **Recommended implementation approach:** 1. **GCS**: Create `connector-file-gcs` module, following the pattern of `connector-file-s3`/`connector-file-oss` 2. **BigQuery**: Create dedicated `connector-bigquery` connector (preferred) or add BigQuery dialect to JDBC connector 3. **AlloyDB**: Test with existing JDBC connector + PostgreSQL driver, then add AlloyDB dialect if needed Since this involves three separate connectors, could you clarify: 1. Which of these three (GCS/BigQuery/AlloyDB) is your highest priority? 2. Are you planning to contribute this feature, or looking for community implementation? -- 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]
