zhangshenghang commented on issue #10339:
URL: https://github.com/apache/seatunnel/issues/10339#issuecomment-3755081044
<!-- code-pr-reviewer -->
Thanks for the proposal. This is a valid feature gap: current Metalake
integration only supports placeholder replacement for credentials, not schema
retrieval from Gravitino.
**Evidence:**
-
`seatunnel-api/src/main/java/org/apache/seatunnel/api/metalake/MetalakeConfigUtils.java`
(L76-84) only fetches properties for placeholder substitution
-
`seatunnel-connectors-v2/connector-mongodb/src/main/java/org/apache/seatunnel/connectors/seatunnel/mongodb/source/MongodbSourceFactory.java`
(L47-52) requires inline `schema` as mandatory
-
`seatunnel-connectors-v2/connector-file/connector-file-base/src/main/java/org/apache/seatunnel/connectors/seatunnel/file/config/BaseFileSourceConfig.java`
(L83-89) uses inline schema or falls back to simple text table
**Suggested starting points:**
1.
`seatunnel-api/src/main/java/org/apache/seatunnel/api/options/table/TableSchemaOptions.java`
— Add `schema_path`, `schema_url` options
2.
`seatunnel-api/src/main/java/org/apache/seatunnel/api/metalake/MetalakeClient.java`
— Add `getTableSchema(String tableRef)` method
3.
`seatunnel-api/src/main/java/org/apache/seatunnel/api/metalake/GravitinoClient.java`
— Implement REST call to `/tables/{table}`
4.
`seatunnel-connectors-v2/connector-file/connector-file-base/src/main/java/org/apache/seatunnel/connectors/seatunnel/file/config/BaseFileSourceConfig.java`
— Extend schema resolution logic
**Questions to clarify:**
1. Should non-relational catalogs (File/ES/MongoDB) use new Gravitino
catalog providers or reuse existing `fileset`/`messaging` types?
2. How should complex types (ES nested/object, MongoDB documents) be mapped
from Gravitino to SeaTunnel data types?
--
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]
