-
Notifications
You must be signed in to change notification settings - Fork 28.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPARK-1478.2: Upgrade FlumeInputDStream's FlumeReceiver to support FLUME-1915 #1168
Conversation
SPARK-1478: Upgrade FlumeInputDStream's FlumeReceiver to support FLUME-1915
Can one of the admins verify this patch? |
Jenkins, this is okay to test. |
Jenkins, test this please. |
Merged build triggered. |
Merged build started. |
Merged build finished. |
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15985/ |
From Jenkins. |
storageLevel: StorageLevel, | ||
enableDecompression: Boolean | ||
): ReceiverInputDStream[SparkFlumeEvent] = { | ||
val inputStream = new FlumeInputDStream[SparkFlumeEvent](ssc, hostname, port, storageLevel, enableDecompression) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This lines is too long.
Thanks tdas I messed that one. I just updated. It should be good now. |
Jenkins, test this please |
Jenkins, add to whitelist |
Merged build triggered. |
Merged build started. |
Merged build finished. |
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16002/ |
This is a weird binary compatibility check failure, that should not be thrown. We are looking at our end for fixing this and rerunning the tests. Once this is figured out, I will merge this. |
Let me know if there is anything I can do to help.
|
Jenkins, test this again. |
Jenkins, test this. |
What is the status of this Jira? |
Jenkins, test this please. |
Merged build triggered. |
Merged build started. |
@tmalaska The binary issue is a pretty tricky issue and doesnt look like it will be fixed any time soon. For now, I am going to try to do work around by ignoring this check (once the latest jenkins build is over, and I have found what to override). Might pull in your changes into my own branch and issue a new PR. |
Got the error, going to fix it. |
Merged build finished. |
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16419/ |
Let me know if I need to do anything |
Done. I closed 566. Anything else. I'm open to work on anything. Just direct me to a jira. |
Ummm. I meant could you close this PR. :) |
…FLUME-1915 This is a modified version of this PR #1168 done by @tmalaska Adds MIMA binary check exclusions. Author: tmalaska <[email protected]> Author: Tathagata Das <[email protected]> Closes #1347 from tdas/FLUME-1915 and squashes the following commits: 96065df [Tathagata Das] Added Mima exclusion for FlumeReceiver. 41d5338 [tmalaska] Address line 57 that was too long 12617e5 [tmalaska] SPARK-1478: Upgrade FlumeInputDStream's Flume...
@tmalaska can you close this? :) |
…FLUME-1915 This is a modified version of this PR apache#1168 done by @tmalaska Adds MIMA binary check exclusions. Author: tmalaska <[email protected]> Author: Tathagata Das <[email protected]> Closes apache#1347 from tdas/FLUME-1915 and squashes the following commits: 96065df [Tathagata Das] Added Mima exclusion for FlumeReceiver. 41d5338 [tmalaska] Address line 57 that was too long 12617e5 [tmalaska] SPARK-1478: Upgrade FlumeInputDStream's Flume...
SPARK-1478.2: Upgrade FlumeInputDStream's FlumeReceiver to support
FLUME-1915