Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/2196
---
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-54267918
@ScrapCodes @nchammas
I merge this PR into #2175 and close this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-54037509
This is okay, but I did not understand the need for a separate PR and JIRA
for same issue. Issue simply applies to both pyspark and spark-shell.
---
If your project
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-54067786
Yeah, that's what I suggested on the linked PR. It makes the set of related
changes atomic, too. But I guess it's not a big deal.
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-53856550
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19469/consoleFull)
for PR 2196 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-53861142
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19469/consoleFull)
for PR 2196 at commit
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2196#issuecomment-53884226
Thanks @witgo!
For others: This PR is related to [this comment on another
PR](https://github.com/apache/spark/pull/2175#issuecomment-53795465).
---
If your
