Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17375
Merged into 1.6
---
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
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17375
LGTM I'll merge this.
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
gentle ping ...
---
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,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
@joshrosen, do you mind if I ask a quick look here? I know you know PySpark
well. I think this backport got a sign-off and a positive comment from both
committers.
---
If your project is set
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
@holdenk Could this be merged maybe?
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/17375
Anaconda default to 3.6 definitely makes this make more sense, thanks
@zero323 I had forgotten that. I'll give @davies until next week to say
anything about this but otherwise I think the set of
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
(gentle ping @holdenk and @davies)
---
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 zero323 commented on the issue:
https://github.com/apache/spark/pull/17375
@holdenk At least some users have more control over Python environment
than a whole cluster setup, and with Anaconda defaulting now to 3.6, it is an
annoyance. Assuming there will be 1.6.4, it
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
Yea, it might be less important but I guess still it is a valid backport.
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/17375
tentative looks good, my only question is if someone wants to use Python
3.6 (first released December 2016) are they likely to want to use it with Spark
1.6 (first released January 2016)?
---
If
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
cc @holdenk too.
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
gentle ping @davies
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
(I will close as soon as it gets merged and the one against branch-2.0 too)
---
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 user davies commented on the issue:
https://github.com/apache/spark/pull/17375
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 and wishes so, or if the
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
cc @davies
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17375
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74972/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17375
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17375
**[Test build #74972 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74972/consoleFull)**
for PR 17375 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17375
**[Test build #74972 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74972/consoleFull)**
for PR 17375 at commit
19 matches
Mail list logo
