Hi Mike, Thank you so much for the warm welcome and the guidance!
The 'middleware' approach makes perfect sense. Building it as a service that interacts with AsterixDB via the REST API keeps the core engine clean and allows for a more flexible LLM integration (like using LangChain4j or direct Gemini API calls). I am now focusing my research on the Metadata Catalog queries in SQL++ to understand how to best feed the schema context to the LLM. @Suryaa, I would love to hear more about the revised UI you are working on. I'd like to ensure my proposal for the NL2SQL bridge aligns perfectly with the new user experience you are envisioning. I'll be drafting my formal proposal based on this 'REST-based Middleware' architecture. Looking forward to more discussions! Best regards, Tanya Rai On Wed, 18 Mar 2026 at 21:40, Mike Carey <[email protected]> wrote: > > Welcome! Entry point wise, this feature should probably live on the > outside of AsterixDB looking in, using its REST-based API to issue its > requests for catalog info (via SQL++ queries) and to submit queries and > get their results. Suryaa can probably comment more on this - he is > working on a revised UI that this would be envisioned as a part of. > > Cheers, > > Mike > > On 3/18/26 5:16 AM, Tanya Rai wrote: > > Hello AsterixDB Team, > > > > I am Tanya Rai, a 2nd-year B.Tech CSE student. I am very interested in > > the Natural Language to SQL (NL2SQL) project for GSoC 2026. > > > > I have successfully set up the project on my Windows machine. To help > > others, I have submitted my first PR which adds a Windows > > Troubleshooting Guide:https://github.com/apache/asterixdb/pull/39. > > > > I am now diving into QueryServiceServlet and the SQL++ grammar to > > understand the best entry point for the NL2SQL layer. I look forward > > to contributing more!
