bring back dev scripts for ballista #648
Merged
Conversation
This file contains 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
alamb
approved these changes
Jun 30, 2021
| @@ -0,0 +1,83 @@ | |||
| #!/usr/bin/env python | |||
There was a problem hiding this comment.
this probably isn't necessary but it also won't hurt - it was used when we had to sync arrow manually with datafusion before there were bi-weekly builds
|
fyi @yjshen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
bring back dev scripts for ballista
Closes #.
Rationale for this change
What changes are included in this PR?
i did a run in
dev/usingto identify any dev files mentioning ballista
Are there any user-facing changes?