diegoscarabelli commented on issue #33215: URL: https://github.com/apache/superset/issues/33215#issuecomment-3054408548
@jpdeloitte that's certainly a good idea as part of the architecture of a Superset AI agent, which isn't really what we are aiming to achieve with this proposal. Our core idea is to build a very simple text-to-sql functionality with the objective to use it as soon as possible. We employed plenty of already available Superset functions to collect schema metadata. Those functions power the SQLLab database explorer on the left-side bar (schemas, tables, columns, data types, SQL comments, constraints, etc.). Our code simply packages this info in a JSON file that is then added to the context of the LLM prompt. This file is built on a schedule and cached for efficiency. Integrating an MCP client will surely be a great follow-up proposal, which will open the door for more than just text-to-sql. For instance, you could envision a Superset chat, with agent properties, that you can talk to and included in its answers is information retrieved from the connected databases. It does seem though an overkill for simple schema-aware text-to-sql, which doesn't include automated execution of the query and a sequence of follow-up LLM interaction to blend the query results into an LLM response or agent action. -- 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
