jpdeloitte commented on issue #33215: URL: https://github.com/apache/superset/issues/33215#issuecomment-3054214518
I'm admittedly over-my-skis a bit here, but it seems like MCP may be a helpful in how this all works. Most DBs have or are in the process of releasing an MCP Server (e.g. https://github.com/awslabs/mcp/tree/main/src/redshift-mcp-server for Redshift). Perhaps this could be architected such that Superset, via a variety of LLMs, talks to those MCP servers (maybe configure the MCP server at the DB connection level..?) to get all necessary metadata on the fly, avoiding the need for the Redis cache and also avoiding the LLM caching limitations...? Either way, super-excited to see where this goes! -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
