[GitHub] spark issue #17709: Small rewording about history server use case

2017-04-20 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17709 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 project does not have this feat

[GitHub] spark issue #17709: Small rewording about history server use case

2017-04-20 Thread guoxiaolongzte
Github user guoxiaolongzte commented on the issue: https://github.com/apache/spark/pull/17709 This PR title should add [DOC]. --- 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 enab

[GitHub] spark issue #17709: Small rewording about history server use case

2017-04-20 Thread HyukjinKwon
Github user HyukjinKwon commented on the issue: https://github.com/apache/spark/pull/17709 Yea, good to match the titles to other PRs and according to the guide lines. It does not block this PR though. --- If your project is set up for it, you can reply to this email and have your re

[GitHub] spark issue #17709: Small rewording about history server use case

2017-04-21 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17709 **[Test build #3668 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3668/testReport)** for PR 17709 at commit [`2560555`](https://github.com/apache/spark/commit/2

[GitHub] spark issue #17709: Small rewording about history server use case

2017-04-21 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/17709 **[Test build #3668 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3668/testReport)** for PR 17709 at commit [`2560555`](https://github.com/apache/spark/commit/

[GitHub] spark issue #17709: Small rewording about history server use case

2017-04-21 Thread srowen
Github user srowen commented on the issue: https://github.com/apache/spark/pull/17709 Merged to master/2.2/2.1 --- 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