tustvold commented on issue #80: URL: https://github.com/apache/arrow-datafusion/issues/80#issuecomment-826914705
> datafusion writes something like ^4.0.0 on its cargo.toml Yes, this would be my ideal for the reasons you articulated. > we release arrow more often and strictly according to semver This would definitely be something I'd be supportive of, but possibly somewhat tangential to making DataFusion as a library easier to consume. Cargo has a good story for overriding dependencies within a workspace, including indirect dependencies, provided those versions aren't pinned within the libraries. Therefore if DataFusion were to move to a released version of arrow it wouldn't preclude users from opting-in to newer, potentially unreleased versions of arrow. However, DataFusion itself would not be able to opt-in to unreleased arrow functionality, and so if there are frequent DataFusion changes coupled with arrow changes, then yes a more frequent arrow release cycle would possibly be a pre-condition of moving to using a released version of arrow. > I am not sure whether we could get away with the multiple paths approach, e.g. I've not come across this approach, I'd worry that it might be vulnerable to https://github.com/rust-lang/cargo/issues/5478 which would prevent users from opting into newer versions of arrow within their workspaces, which imo would be unfortunate -- 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]
