Coding-Alchemist-Abhijay commented on issue #9472: URL: https://github.com/apache/gravitino/issues/9472#issuecomment-3646903112
Right now, loading a catalog or schema requires multiple sequential API calls (Metalake ā Catalog ā Schema), which increases latency and adds unnecessary complexity on the client side. For example, loading a schema requires: Loading the Metalake and retrieving its ID Using that ID + catalog name to load the Catalog Using the Catalog ID + schema name to fetch the Schema To improve this, I propose adding support for join-based lookups so that these entities can be resolved in a single request. This would allow the backend to perform the necessary joins internally, significantly reducing round-trips and improving response time. My plan is to: Introduce a new lookup API that accepts compound identifiers (e.g., metalakeName/catalogName/schemaName). Implement backend join logic to resolve all required entities at once. Ensure proper indexing to keep the joined queries efficient. Add tests and documentation so users clearly understand the new, simplified workflow. This would streamline the experience and remove the need for clients to manually chain multiple calls. Please assign this issue to me ā Iād be happy to work on the design and 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]
