yuqi1129 commented on PR #12114: URL: https://github.com/apache/gravitino/pull/12114#issuecomment-5031927828
If this capability is genuinely needed now, I suggest adding a dedicated search API to Gravitino Server first, and then having the MCP tool act as a thin wrapper around that API. This keeps metadata discovery semantics, authorization, pagination, and performance controls in Gravitino rather than implementing them independently in the MCP server. The server API should be backed by an appropriate metadata index or inventory; moving the same nested crawl behind a new endpoint would not address the scalability issue. -- 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]
