alamb commented on pull request #68: URL: https://github.com/apache/arrow-datafusion/pull/68#issuecomment-930034589
> But from the activities I have observed in the arrow2 repo so far This is great information -- thank you for sharing it @houqp . > so I am concerned that moving to ASF at its current stage would slow him down unless we start to get significant more contributions to the arrow2 repo. Yeah - it is definitely a 2 edged sword -- I suspect moving arrow2 to ASF would indeed slow @jorgecarleitao down but also would encourage more contributions. Balancing that tradeoff is trickey for sure. > If we don't want to pay the cost of maintaining a separate arrow2 datafusion branch, we could also temporarily have datafusion depend the current arrow2 repo with the goal of eventually merging arrow2 with arrow as it matures. Since datafusion relies on arrow, if we change it to rely on arrow2, any downstream projects that rely on datafusion that want to use the latest datafusion will also have to change to use arrow2 (to feed data in the `MemoryProvider`, for example). I think this is what you mean by "downstream impact" Thus I would prefer we continue datafusion with a stable implementation of arrow -- and we can wait until that describes arrow2. -- 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]
