roryqi opened a new issue, #13281:
URL: https://github.com/apache/gravitino/issues/13281

   ### What would you like to be improved?
   
   `gravitino.metalake` is currently required by the Trino connector, even 
though multi-metalake mode can already discover metalakes through 
`listMetalakes()`.
   
   When `gravitino.metalake` is not configured, the connector should start 
successfully and load catalogs from all accessible metalakes instead of 
reporting a missing configuration error.
   
   ### How should we improve?
   
   - Make `gravitino.metalake` optional.
   - Preserve the existing behavior when `gravitino.metalake` is configured.
   - When it is not configured, discover all accessible metalakes and load 
their catalogs.
   - Use the existing multi-metalake catalog naming convention, 
`<metalake_name>.<catalog_name>`, to avoid collisions.
   - Keep catalog creation, deletion, and metadata refresh synchronized across 
metalakes.
   - Add unit and integration tests and update the Trino connector 
documentation.
   


-- 
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]

Reply via email to