Data loader fixes#7672
Merged
clintropolis merged 4 commits intoapache:0.15.0-incubatingfrom May 19, 2019
Merged
Conversation
Contributor
Author
|
Ok now that the mentioned PRs were merged this is essentially straight up a backport |
jihoonson
pushed a commit
to implydata/druid-public
that referenced
this pull request
Jun 4, 2019
* add ability to submit 'other' task * copy changes, fix sort * lets call it dialog * update name to Google Cloud Storage
gianm
added a commit
to implydata/druid-public
that referenced
this pull request
Jul 4, 2019
This reverts commit ba6caf5.
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
3 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.
Making a bugfix PR for the data loader and sorting issue for the 0.15.0 release
Due to changes that have already been merged into master and the changes that are coming in #7643 it does not make sense to merge this into master.
Technically porting this fix or merging #7643 will have to be a release blocker for the 0.16.0 release.
Fixes here: