Omega359 opened a new issue, #9164: URL: https://github.com/apache/arrow-datafusion/issues/9164
### Describe the bug internal_err! is used as a general error macro in many spots in the code where in fact the problem the error is propagating is not caused by an oversight, bug, etc in the code but rather by user error. A good example of this can be seen in PR #9137 [comment](https://github.com/apache/arrow-datafusion/pull/9137#discussion_r1480303798) where it's being used to let the user know they provided a datatype as an argument to a function that it doesn't support. This in fact should be an exec_err! in this example. ### To Reproduce _No response_ ### Expected behavior In most cases where the error is caused by incorrect data types or invalid argument counts exec_err! should be used. ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
