Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64389631
@watermen Thanks these are great fixes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64389589
Jenkins, this is ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64390206
[Test build #23838 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23838/consoleFull)
for PR 3400 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64398984
[Test build #23838 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23838/consoleFull)
for PR 3400 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-64398987
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3400
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user watermen opened a pull request:
https://github.com/apache/spark/pull/3400
[SPARK-4535][Streaming] Fix the error in comments
change `NetworkInputDStream` to `ReceiverInputDStream`
change `ReceiverInputTracker` to `ReceiverTracker`
You can merge this pull request into
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3400#issuecomment-63943505
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
