Refactor Ballista executor so that FlightService delegates to an Executor struct#450
Merged
alamb merged 5 commits intoapache:masterfrom May 31, 2021
Merged
Conversation
Member
Author
|
@edrevo fyi |
Codecov Report
@@ Coverage Diff @@
## master #450 +/- ##
=======================================
Coverage 75.16% 75.17%
=======================================
Files 150 151 +1
Lines 25142 25140 -2
=======================================
Hits 18899 18899
+ Misses 6243 6241 -2
Continue to review full report at Codecov.
|
edrevo
approved these changes
May 31, 2021
Dandandan
approved these changes
May 31, 2021
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
6 participants
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 #449 .
Rationale for this change
This is fixing some tech debt so that the executor doesn't have to connect to itself over Flight to run queries.
What changes are included in this PR?
Are there any user-facing changes?
No