Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4822
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/4822#issuecomment-76534947
I'd like to merge this in the next day or two as I think I agree that this
could be a blocker. I think it's straightforward but invite a third set of eyes
to take a look.
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/4822#issuecomment-76563416
Good catch @vanzin. This LGTM. I did some testing to verify that the
assembly includes all relevant python files now:
```
$ jar -tf
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4822#issuecomment-76509271
[Test build #28106 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28106/consoleFull)
for PR 4822 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4822#issuecomment-76506844
[Test build #28106 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28106/consoleFull)
for PR 4822 at commit
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/4822
[SPARK-6074] [sql] Package pyspark sql bindings.
This is needed for the SQL bindings to work on Yarn.
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4822#issuecomment-76509272
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4822#issuecomment-76506782
$ jar tf sql/core/target/spark-sql_2.10-1.3.0-SNAPSHOT.jar | grep
pyspark
pyspark/
pyspark/sql/
pyspark/sql/functions.py
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4822#issuecomment-76509136
That seems like the right way to do this thing. It mirrors similar
declarations for core, mllib, streaming, etc. Should `tests.py` be in here?
Maybe not worth bothering
