Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-58774750
Should we create a JIRA for this task?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-58775530
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21661/consoleFull)
for PR 2762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2773#issuecomment-58775579
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2773#issuecomment-58775578
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21659/consoleFull)
for PR 2773 at commit
Github user tigerquoll commented on the pull request:
https://github.com/apache/spark/pull/2516#issuecomment-58775682
Hi @vanzin, I've implemented your suggestions, tidied up the code more, and
also added more unit tests to flesh out the test coverage.
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58775688
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21660/consoleFull)
for PR 2538 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58775690
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tigerquoll commented on the pull request:
https://github.com/apache/spark/pull/2516#issuecomment-58775741
@andrewor14 we could be stepping on each other's toes soon. Have a query
about your work on Utils.ResolveUris. I notice that you produce and test for
file URIs with
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2761#issuecomment-58776141
I also think, it's difficult to apply new style checker only to new codes.
I cleaned up codes in origin/master for the style checker suggested in this PR.
So, if this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-58776261
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21661/consoleFull)
for PR 2762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2762#issuecomment-58776263
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58776274
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21663/consoleFull)
for PR 2728 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2755#issuecomment-58776269
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21662/consoleFull)
for PR 2755 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58776270
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21663/consoleFull)
for PR 2728 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2755#issuecomment-58776275
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2755#issuecomment-58776273
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21662/consoleFull)
for PR 2755 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58776276
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-58776387
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21664/consoleFull)
for PR 2520 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2755#issuecomment-58776421
retest this please.
---
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
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58776416
retest this please.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2755#issuecomment-58776471
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21665/consoleFull)
for PR 2755 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58776475
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21666/consoleFull)
for PR 2728 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-58778031
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-58778022
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21664/consoleFull)
for PR 2520 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2755#issuecomment-58778333
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21665/consoleFull)
for PR 2755 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2755#issuecomment-58778334
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58783062
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58783054
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21666/consoleFull)**
for PR 2728 at commit
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58783286
Alright, I am merging this!! This is awesome, great great work @giwa and
@davies. Thank a lot to both of you, and also to @JoshRosen for ongoing help,
suggestions and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2538
---
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 giwa commented on the pull request:
https://github.com/apache/spark/pull/2538#issuecomment-58795386
Thank you for merging this! I appreciate to you, @tdas , to give me many
advices. Thank you, @davies to refactor code a lot. I learned many thing from
your commits. And
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/2774
[SPARK-2066][SQL] Adds checks for non-aggregate attributes with aggregation
This PR adds a new rule `CheckAggregation` to the analyzer to provide
better error message for non-aggregate attributes
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58797661
Can one of the admins verify this patch?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58797810
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21667/consoleFull)
for PR 2774 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58798685
retest this please.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58798823
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21668/consoleFull)
for PR 2728 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58800409
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58800408
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21667/consoleFull)
for PR 2774 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58800896
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21669/consoleFull)
for PR 2774 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2761#issuecomment-58801175
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21670/consoleFull)
for PR 2761 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58801346
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21669/consoleFull)
for PR 2774 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58801348
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58802243
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21671/consoleFull)
for PR 2774 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58802491
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21668/consoleFull)
for PR 2728 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-58802496
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58802716
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58802712
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21671/consoleFull)
for PR 2774 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2761#issuecomment-58805927
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21670/consoleFull)
for PR 2761 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2761#issuecomment-58805931
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2564#issuecomment-58806389
Hi @tdas, does this look OK to you? Ready to go from this end. Just a
little minor change to examples but I agree it's a worth example to resurrect.
---
If your project
GitHub user omgteam opened a pull request:
https://github.com/apache/spark/pull/2775
Bug Fix: without unpersist method in RandomForest.scala
During trainning Gradient Boosting Decision Tree on large-scale sparse
data, spark spill hundreds of data onto disk. And find the bug below:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2775#issuecomment-58808512
Can one of the admins verify this patch?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2775#issuecomment-58808516
Can one of the admins verify this patch?
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/2741#issuecomment-58808996
LGTM. Is it worth to add `val UTF8 = Charset.forName(UTF-8)` into `object
Utils`?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user surendramarupudi commented on the pull request:
https://github.com/apache/spark/pull/1717#issuecomment-58811881
Hi, I am trying to use this new location feature
TwitterUtils.createStream(ssc,filters,double[][]) for this filters are working
but filtering for location is
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/2776
[HOTFIX] Fix compilation error for Yarn 2.0.*-alpha
This was reported in https://issues.apache.org/jira/browse/SPARK-3445.
You can merge this pull request into a Git repository by running:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2776#issuecomment-58817786
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21672/consoleFull)
for PR 2776 at commit
GitHub user elmalto opened a pull request:
https://github.com/apache/spark/pull/2777
[Docs] logNormalGraph missing partition parameter
closed old pull request, updated parameters
You can merge this pull request into a Git repository by running:
$ git pull
Github user elmalto closed the pull request at:
https://github.com/apache/spark/pull/2523
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2777#issuecomment-58817946
Can one of the admins verify this patch?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2777#issuecomment-58817953
Can one of the admins verify this patch?
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/2727#issuecomment-58818313
@marmbrus ready to merge?
---
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-58819971
Jenkins, test this please.
---
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 user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-58820059
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21673/consoleFull)
for PR 2770 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2741#issuecomment-58820370
I'm merging this in 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 user rxin commented on the pull request:
https://github.com/apache/spark/pull/2741#issuecomment-58820340
It is probably good to add, but maybe in a separate PR?
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/2753#discussion_r18749775
--- Diff:
core/src/main/scala/org/apache/spark/network/BlockFetchingListener.scala ---
@@ -31,7 +34,7 @@ trait BlockFetchingListener extends EventListener {
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2741
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2776#issuecomment-58821198
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21672/consoleFull)
for PR 2776 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2776#issuecomment-58821201
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-58821270
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21673/consoleFull)
for PR 2770 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2770#issuecomment-58821272
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/2777#issuecomment-58822691
e5d376801d57dffb0791980a1786a0a9b45bc491 changed logNormalGraph so that
it's no longer strictly necessary to pass `numEParts = sc.defaultParallelism`
because it will
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/2569#issuecomment-58823498
Thanks, merged into branch-1.1 and cherry-picked into master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2569
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2776#issuecomment-58825253
Tested build on 0.23.7 and 2.0.6-alpha. I'm merging this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2776
---
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 giwa opened a pull request:
https://github.com/apache/spark/pull/2778
Add echo Run streaming tests ...
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/giwa/spark patch-2
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2778#issuecomment-58829743
Can one of the admins verify this patch?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2778#issuecomment-58829747
Can one of the admins verify this patch?
---
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 chouqin commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-58836687
@manishamde @jkbradley I have created a JIRA for supporting both
options([SPARK-3920](https://issues.apache.org/jira/browse/SPARK-3920)). I am
dealing with
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-58836896
Thanks @chouqin Please get those tickets assigned to your from @mengxr to
ensure nobody else works on it in parallel.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58839896
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21674/consoleFull)
for PR 2774 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58842623
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2774#issuecomment-58842619
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21674/consoleFull)
for PR 2774 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2778#issuecomment-58844415
Jenkins, add to whitelist.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2778#issuecomment-58844807
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21675/consoleFull)
for PR 2778 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58845062
This looks great; thanks for adding the comments. I'm going to merge this
into master and backport it to `branch-1.0` and `branch-1.1`.
---
If your project is set up
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2712
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/2775#issuecomment-58846317
Jenkins, this is ok to test.
---
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 user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2775#issuecomment-58846485
LGTM. Waiting for Jenkins. Unreferenced RDDs will get cleaned
automatically. But it is always good to call `unpersist` explicitly.
---
If your project is set up for it,
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2775#issuecomment-58846495
test this please
---
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
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-58846802
@chouqin Thanks for tackling these issues! I'm reworking the spark-perf
suite to support real datasets and will resume on timing tests once that it
done.
---
If
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2595#issuecomment-58847036
Let's move our discussion to SPARK-3920. I think we need more testing
before we decide to provide both options. Maybe there are some optimization we
can do with the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2775#issuecomment-58847098
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-58847116
@manishamde It looks like the failure was in compilation:
```
[error]
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2749#issuecomment-58848075
Good catch. Do you mind updating this to link to the
`#implementing-and-using-a-custom-actor-based-receiver` anchor on the new page?
---
If your project is set up
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2763#issuecomment-58848203
Wow, good catch! I'm very surprised that this problem wasn't caught
earlier. I'm going to merge this into `master` and look into backporting it to
the other
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2763
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2778#issuecomment-58848771
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21675/consoleFull)
for PR 2778 at commit
1 - 100 of 101 matches
Mail list logo
