comphead opened a new issue, #7360: URL: https://github.com/apache/arrow-datafusion/issues/7360
### Is your feature request related to a problem or challenge? I'm trying to collect known issues related to error handling in datafusion. So far I can see different categories which can be improved 1. DataFusion heavily relies on Rust `Result<T, E>` and sometimes its hard to identify context where the actual error is happening, the situation becomes even worse for downstream projects. - [ ] https://github.com/apache/arrow-datafusion/issues/5283 - [ ] https://github.com/apache/arrow-datafusion/issues/3410 (this related to upstream arrow-rs) 2. Overuse panics - [ ] https://github.com/apache/arrow-datafusion/issues/3313 - [ ] https://github.com/apache/arrow-datafusion/issues/3317 - [ ] https://github.com/apache/arrow-datafusion/issues/3316 3. Overuse internal error type in situations where more specific error kind can be used - [ ] https://github.com/apache/arrow-datafusion/issues/6108 ### Describe the solution you'd like We can try to address some of the issues with implementing a generic error macros that will be used for handling DF errors. Having done that allows to process errors in standard unified way, experiment with stacktraces and other details needed to be exposed for the end user. - [ ] https://github.com/apache/arrow-datafusion/pull/7115 - [ ] https://github.com/apache/arrow-datafusion/pull/7293 - [ ] https://github.com/apache/arrow-datafusion/pull/7340 - [ ] Execution Error macros - [ ] Arrow Error macros - [ ] SQL Error macros - [ ] Parquet Error macros - [ ] ObjectStore Error macros - [ ] IOError macros - [ ] Schema Error macros - [ ] ResourceExhausted Error macros - [ ] External Error macros - [ ] Context Error macros - [ ] Substrait Error macros ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
