Repository navigation
Conversation
This was referenced May 27, 2022
Contributor
Author
|
Actually I don't think this will work as the breaking arrow changes will likely still break ballista... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
I don't particularly like this, but this will allow Ballista to automatically pick up the compatible version of arrow-flight to use with the version of arrow used by DataFusion. Alternative suggestions welcome...
What changes are included in this PR?
Adds a new
flightfeature todatafusionthat enables a re-export of a compatible arrow_flight versionAre there any user-facing changes?
No
Does this PR break compatibility with Ballista?
No