EmilyMatt opened a new issue, #1513: URL: https://github.com/apache/datafusion-comet/issues/1513
### What is the problem the feature request solves? There are many redundant dependencies in the project's Cargo.toml files at the moment. I believe almost all datafusion-X crates can be removed from the dependencies and be directly accessed from the main datafusion crate (I believe I've seen only one instance in which datafusion_common was needed as those specific functions weren't exported, but i'm pretty sure even then they could have been modified to not need it) The same goes for all the arrow-X crates, all the required structs are available via arrow::X I think it both makes the dependency tree cleaner, and allows easier maintenance (I.e., modifying a single version instead of many etc) I believe all features can be accessed via the main crate as well. But perhaps there's a reason I'm not aware of which is why this was chosen. ### Describe the potential solution Simply removing all the datafusion_X and arrow_X crates, In the absolute majority of cases even a simple search-and-replace of "arrow_data::" to "arrow::data::" is sufficient, but some things like arrow_schema::SchemaRef need to be accessed using arrow::datatypes::SchemaRef, and arrow::array::ArrayData likewise. still, that is a rather cheap fix. ### 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: github-unsubscr...@datafusion.apache.org.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
