[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-05-02 Thread zsxwing
Github user zsxwing commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-216351937 > This PR is not merged with branch-1.6. Is there a reason for it? @sarathjiguru as we have already merged workarounds to branch-1.6, it's not necessary to

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-04-26 Thread sarathjiguru
Github user sarathjiguru commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-214703438 Hello @zsxwing , This PR is not merged with branch-1.6. Is there a reason for it? I am hoping latest version of py4j is needed for production ready

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-12 Thread zsxwing
Github user zsxwing commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-171077147 @davies could you take a look at my latest commit? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-12 Thread davies
Github user davies commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-171078513 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] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-12 Thread zsxwing
Github user zsxwing commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-171079982 Thanks, merging to master --- 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] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-12 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/10692 --- 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] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170728862 **[Test build #49188 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49188/consoleFull)** for PR 10692 at commit

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170748811 **[Test build #49188 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49188/consoleFull)** for PR 10692 at commit

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170749031 Merged build finished. Test PASSed. --- 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] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread zsxwing
Github user zsxwing commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170748911 @JoshRosen @davies could you take a look? --- 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] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170749033 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread davies
Github user davies commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170754853 @zsxwing Could you also update the patch for callback server to use new API? see https://github.com/bartdag/py4j/issues/147 --- If your project is set up for it, you

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170827125 Test PASSed. Refer to this link for build results (access rights to CI server needed):

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170826809 **[Test build #49215 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49215/consoleFull)** for PR 10692 at commit

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170827117 Merged build finished. Test PASSed. --- 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] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread zsxwing
Github user zsxwing commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170801917 > @zsxwing Could you also update the patch for callback server to use new API? see bartdag/py4j#147 Updated --- If your project is set up for it, you can

[GitHub] spark pull request: [SPARK-12652][PySpark]Upgrade Py4J to 0.9.1

2016-01-11 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/10692#issuecomment-170805649 **[Test build #49215 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49215/consoleFull)** for PR 10692 at commit