tustvold commented on issue #2709: URL: https://github.com/apache/arrow-datafusion/issues/2709#issuecomment-1167943585
> AFAIK governance has not been a factor when considering dependencies in DataFusion To conflate arrow which is core to both the in-memory layout and query computation, with something fairly self-contained like `smallvec`, `chrono` or `ahash` I think is a wee bit disingenuous :sweat_smile: It is fairly common for work in arrow-datafusion to build upon/require work in arrow-rs, whereas the same is not true of those listed dependencies. Given we are still talking about this I think we have clearly demonstrated arrow is not a trivial dependency, and therefore warrants some additional care and attention... > was to use traits to collect the differences in the two apis -- so that DataFusion used the traits and then there were impls for both arrow and arrow2 If practicable this sounds like a good idea to me. It would also fit with my ongoing efforts, articulated [here](https://github.com/apache/arrow-rs/issues/1176), to gradually bring incubated ideas from arrow2 to arrow-rs. I'm actually pretty happy with the progress that has been made so far, and having an easy way to compare the two implementations I think would prove insightful. In particular I have been inspired by the way the arrow-rs community has worked together to drive progress, through code contributions or otherwise. Yes arrow-rs still has many warts, and is often not particularly pleasant to work on, but there is an active community of people working to make it better in whatever ways they can, and that to me is what open source is all about. For some the governance question is one of legal practicalities, but at least for me it is about having a friendly community working together to deliver great software. -- 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]
