-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attach Diagnostic
to "invalid function argument types" error
#14431
Comments
Diagnostic
to "invalid function argument types" error
Hi I'm interested in this ticket. Could you please assign it to me? If you think my progress slow, feel free to ping me any time, I will try to prioritize and expedite. Thank you! |
@dentiny Absolutely! Though I don't have the permissions to assign it to you, you can write |
take |
I think this is a good first issue as the need is clear and the tests in https://github.com/apache/datafusion/blob/85fbde2661bdb462fc498dc18f055c44f229604c/datafusion/sql/tests/cases/diagnostic.rs are well structured for extension. |
Hey @dentiny how is it going with this ticket :) Can I help with anything? |
Hi @eliaperantoni thanks for checking! I'm still playing around df these days, should be able to get sth by EOW, do you think it's ok for you? |
Absolutely! I'm here if you need any help :) |
Checking the code, I found for "invalid argument type" error there're quite a few places we need to update; |
Is your feature request related to a problem or challenge?
For a query like:
The only message that the end user of an application built atop of DataFusion sees is:
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:
See #14429 for more information.
Describe the solution you'd like
Attach a well crafted
Diagnostic
to theDataFusionError
, building on top of the foundations laid in #13664. See #14429 for more information.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: