Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13520
Thank you, @rxin !
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/13520
Merging in master/2.0.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13520
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60319/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13520
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/13520
**[Test build #60319 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60319/consoleFull)**
for PR 13520 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13520
**[Test build #60319 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60319/consoleFull)**
for PR 13520 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13520
Since this is about examples, I think the shorter is the better.
Users can think simply `parallelize` or `broadcast` are just one of
functions without knowing `SparkContext`.
---
If your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13520
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13520
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60192/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13520
**[Test build #60192 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60192/consoleFull)**
for PR 13520 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13520
**[Test build #60192 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60192/consoleFull)**
for PR 13520 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13520
I'm a little positive on this so would like to merge if there aren't
stronger objections.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13520
Thank you, @srowen !
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13520
Initially, I thought the printed message was wrong in the statement
`println("Creating SparkContext")` because `spark.sparkContext` is just to
return the already existing one.
---
If your
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13520
var -> val seems fine if it's changed while touching related code anyway.
That's a reasonable point about putting the focus on 'spark', yeah.
---
If your project is set up for it, you can reply
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13520
Thank you for review, @rxin and @srowen .
The main rational of this PR is to make `SparkSession` explicitly as a
starting point for the operations in these examples. (Instead of
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13520
I'm neutral on it. It removes a variable, sure, but means writing a longer
expression repeatedly later.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13520
@dongjoon-hyun sorry for asking, but what's the value of this change?
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13520
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60014/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13520
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/13520
**[Test build #60014 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60014/consoleFull)**
for PR 13520 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13520
**[Test build #60014 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60014/consoleFull)**
for PR 13520 at commit
22 matches
Mail list logo
