alamb opened a new pull request #395: URL: https://github.com/apache/arrow-datafusion/pull/395
# Which issue does this PR close? Closes https://github.com/apache/arrow-datafusion/issues/393 # Rationale for this change Currently datafusion relies on a git sha of the arrow-rs crate. Historically this was required to get updates on a more frequent basis than every quarter when Arrow did major releases. With https://github.com/apache/arrow-rs/issues/292 we are implementing biweekly arrow releases. This also means prior to this PR that any project that uses datafusion and arrow together requires pinning arrow-rs to the exact same gitsha. <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> # What changes are included in this PR? Pin to `arrow-rs` "version 4.0" However, given the way cargo interprets versions, this (somewhat confusingly) means the latest "4.x" release. You can see that 4.1 (the most recently released version of arrow-rs) is used by doing something like ``` cargo update cargo tree | grep arrow ... ├── arrow v4.1.0 (*) ... ``` # Are there any user-facing changes? Yes -- the version of arrow-rs used by dependent projects needs to be updated to be 4.0 (or some variant) as well. However, this is no different than what has happened previously when we updated the git sha (dependent crates needed to follow the sha exactly). This should make future datafusion upgrades easier as arrow dependent versions will only need to be updated on major releases, not each datafusion release -- 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. For queries about this service, please contact Infrastructure at: [email protected]
