Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10633#issuecomment-169575922
For this one it is probably OK. We can just merge it (into master &
branch-1.6).
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10633#issuecomment-169572318
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
Github user zzcclp commented on the pull request:
https://github.com/apache/spark/pull/10633#issuecomment-169571829
@JoshRosen
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10633
---
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/10633#issuecomment-169573818
LGTM
---
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
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10633#issuecomment-169574052
@zzcclp Could you file this issue in JIRA and modify the title of this PR
like `[SPARK-][DOC]fix...` ?
---
If your project is set up for it, you can reply to this
