eliaperantoni opened a new issue, #14437: URL: https://github.com/apache/datafusion/issues/14437
### Is your feature request related to a problem or challenge? For a query like: ```sql WITH cte AS (SELECT 1 AS col), SELECT * FROM cte ``` The only message that the end user of an application built atop of DataFusion sees is: ``` SQL error: ParserError("Expected: AS, found: * at Line: 1, Column: 39") ``` We want to provide a richer message that _references and highlights locations in the original SQL query_, and contextualises and helps the user understand the error. In the end, it would be possible to display errors in a fashion akin to what was enabled by #13664 for some errors: ![](https://github.com/user-attachments/assets/32efeb4f-aad9-41c9-a1e3-600a00d525c3) See #14429 for more information. ### Describe the solution you'd like Attach a well crafted `Diagnostic` to the `DataFusionError`, building on top of the foundations laid in #13664. See #14429 for more information. The location of the error can probably be fetched from the error coming from `sqlparser`, requiring little changes to DataFausion itself. Needs some thought to figure out which kinds of syntax errors can be supported and how. i.e. the example above is simply for when the parser expects token in a specific set; but what about unbalanced parenthesis, unrecognised keywords, etc. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- 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: github-unsubscr...@datafusion.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org