[SPARK-18114][HOTFIX] Fix line-too-long style error from backport of SPARK-18114 #15719
Conversation
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
Contributor
|
Merging in branch-2.0. I'm waiting for this to cut rc2. |
asfgit
pushed a commit
that referenced
this pull request
Nov 1, 2016
…PARK-18114 ## What changes were proposed in this pull request? Fix style error introduced in cherry-pick of #15643 to branch-2.0. ## How was this patch tested? Existing tests Author: Sean Owen <sowen@cloudera.com> Closes #15719 from srowen/SPARK-18114.2.
Member
Author
|
Yep, sorry for this right in the middle of RC time. The change itself should be a perfectly fine bug fix. |
Contributor
|
Can you close this? |
|
Test build #67914 has finished for PR 15719 at commit
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
What changes were proposed in this pull request?
Fix style error introduced in cherry-pick of #15643 to branch-2.0.
How was this patch tested?
Existing tests