Is your feature request related to a problem or challenge?
The current categories under DataFusionError is not Mutually Exclusive, Collectively Exhaustive (MECE), making it hard to use consistently.
For example, if the user is developing a custom Object Store, should they return DataFusionError::ObjectStore, DataFusionError::IoError, or DataFusionError::External? Similarly, for an error happened during the plan stage of a custom TableProvider, should that be DataFusionError::Plan, or DataFusionError::External?
The "Collectively Exhaustive" part can be hard, since one cannot predict all the possible errors; however the Mutually Exclusive property should still hold.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
Is your feature request related to a problem or challenge?
The current categories under DataFusionError is not Mutually Exclusive, Collectively Exhaustive (MECE), making it hard to use consistently.
For example, if the user is developing a custom Object Store, should they return DataFusionError::ObjectStore, DataFusionError::IoError, or DataFusionError::External? Similarly, for an error happened during the plan stage of a custom TableProvider, should that be DataFusionError::Plan, or DataFusionError::External?
The "Collectively Exhaustive" part can be hard, since one cannot predict all the possible errors; however the Mutually Exclusive property should still hold.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response