DanielCarter-stack commented on issue #10553: URL: https://github.com/apache/seatunnel/issues/10553#issuecomment-3985416099
<!-- code-pr-reviewer --> Thank you for your willingness to contribute! The proposal overlaps with SeaTunnel's existing Gravitino integration. Currently, `MetaLakeFactory` (`seatunnel-api/src/main/java/org/apache/seatunnel/api/metalake/MetaLakeFactory.java`) already provides Gravitino-based metadata management, and `EnvCommonOptions` (`seatunnel-api/src/main/java/org/apache/seatunnel/api/options/EnvCommonOptions.java:120-137`) supports `metalake` configuration. To clarify the scope of this new **DataSource Center SPI**, could you please specify: 1. **What exact problem does this solve** that the existing `MetaLakeFactory` does not? (e.g., centralizing connection credentials across jobs vs. schema discovery) 2. **What operations should the SPI support**? (e.g., register/deregister datasources, retrieve connection info, encrypt credentials) 3. **How would configuration look**? (e.g., referencing a datasource ID via `env.datasource_center` vs. current inline connector options) Providing a concrete example (such as a JDBC connector use case) would help the community understand the intended design and distinguish it from the current architecture. -- 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]
