berkaysynnada commented on PR #15371:
URL: https://github.com/apache/datafusion/pull/15371#issuecomment-2747189798
We can keep this change specific to our fork, but I believe organizing
datafusion such will make things clearer and more accessible.
TLDR: datasinks and datasources are sibling executors that handle IO
operations, and they may need to access many common utilities. Keeping them
together improves cohesion.
This is the updated dep graph for easier visualization:
```mermaid
graph TD
Catalog --> Session
Datasource --> Session
Catalog --> Datasource
Datasource --> PhysicalPlan
Session --> PhysicalPlan
PhysicalPlan --> Execution
Catalog:::top
Session:::mid
Datasource:::mid
PhysicalPlan:::leaf
Execution:::leaf
```
Only question in my mind is whether we should rename the crate
--
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
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
