Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156357307
Jenkins, 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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156357077
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156357018
**[Test build #45837 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45837/consoleFull)**
for PR 9684 at commit
[`85d18d2`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156357076
Merged build finished. Test FAILed.
---
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/9686#issuecomment-156356474
[Test build #45841 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45841/consoleFull)
for PR 9686 at commit
[`7e83298`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9687#issuecomment-156356492
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9688#issuecomment-156356501
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9688#issuecomment-156356489
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9687#issuecomment-156356500
Merged build started.
---
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/9390#issuecomment-156356266
**[Test build #45836 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45836/consoleFull)**
for PR 9390 at commit
[`65b3d16`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-156356304
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-156356303
Merged build finished. Test FAILed.
---
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9688#issuecomment-156356290
cc @marmbrus
---
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 featur
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9688
[SPARK-11654][SQL][follow-up] fix some mistakes and clean up
* rename `AppendColumn` to `AppendColumns` to be consistent with the
physical plan name.
* clean up stale comments.
* always pa
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/9687
[SPARK-11677][SQL ]ORC filter tests all pass if filters are actually not
pushed down.
Currently ORC filters are not tested properly. All the tests pass even if
the filters are not pushed down o
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156356056
**[Test build #45843 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45843/consoleFull)**
for PR 9658 at commit
[`d17a2db`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9685#issuecomment-156355846
**[Test build #45842 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45842/consoleFull)**
for PR 9685 at commit
[`9aa668c`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9685#issuecomment-156355394
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156355396
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9685#issuecomment-156355367
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9686#issuecomment-156355395
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156355368
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9686#issuecomment-156355365
Merged build triggered.
---
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 h
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156355260
All the builds pass all the tests at `ParquetIOSuite` and I do not think it
affects other modules such as ML.
I will retest this.
---
If your project is set up
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156355277
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 davies commented on the pull request:
https://github.com/apache/spark/pull/9686#issuecomment-156354971
cc @andrewor14
---
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 davies opened a pull request:
https://github.com/apache/spark/pull/9686
[SPARK-8029] robust shuffle writer
Currently, all the shuffle writer will write to target path directly, the
file could be corrupted by other attempt of the same partition on the same
executor. They
GitHub user nongli opened a pull request:
https://github.com/apache/spark/pull/9685
[SPARK-11724] [SQL] Change casting between int and timestamp to consiâ¦
â¦stently treat int in seconds.
The current behavior is odd but there were a few tests that verified it.
Not sure if
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9060#issuecomment-156354310
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9060#issuecomment-156354309
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9060#issuecomment-156354224
**[Test build #45831 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45831/consoleFull)**
for PR 9060 at commit
[`78449ec`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156353605
**[Test build #45840 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45840/consoleFull)**
for PR 9651 at commit
[`240bcf3`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-156352280
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-156352217
**[Test build #45833 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45833/consoleFull)**
for PR 9165 at commit
[`acb987a`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-156352278
Merged build finished. Test FAILed.
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156351030
Hopefully PR #9677 fixes the flaky MLlib tests.
---
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/9651#issuecomment-156350581
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156350536
Merged build triggered.
---
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 h
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9591#discussion_r4474
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/GroupedDataset.scala
---
@@ -137,8 +137,19 @@ class GroupedDataset[K, T] private[sql](
}
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156349621
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 f
Github user Tarrasch commented on the pull request:
https://github.com/apache/spark/pull/9647#issuecomment-156347814
> I don't know that in general Spark scripts work at all with zsh.
You launch a binary, you don't source a script. The shell you invoke a
binary from doesn't ma
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9288#issuecomment-156347361
@andrewor14 , from my understanding this wrong ordering is happened when
driver explicitly abort the running stages because of exceeding max failures.
So `SparkListene
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156346392
Merged build finished. Test FAILed.
---
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 pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156346396
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156346131
**[Test build #45838 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45838/consoleFull)**
for PR 9651 at commit
[`240bcf3`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156345451
Merged build finished. Test FAILed.
---
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/9658#issuecomment-156345230
**[Test build #45835 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45835/consoleFull)**
for PR 9658 at commit
[`d17a2db`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156345454
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7888#issuecomment-156343707
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7888#issuecomment-156343387
**[Test build #45829 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45829/consoleFull)**
for PR 7888 at commit
[`551`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7888#issuecomment-156343702
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
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9665#issuecomment-156343148
This is a bit of breaking the semantics of current Spark Streaming. Besides
why only in direct Kafka stream if this targets to a general solution.
---
If your project
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/8848#issuecomment-156342123
ok thanks.
---
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 featu
Github user KaiXinXiaoLei closed the pull request at:
https://github.com/apache/spark/pull/8848
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9214
---
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 enab
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9610#issuecomment-156341753
**[Test build #2054 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2054/consoleFull)**
for PR 9610 at commit
[`71b12bf`](https://git
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9610
---
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 enab
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9589#issuecomment-156341657
**[Test build #45839 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45839/consoleFull)**
for PR 9589 at commit
[`6203bc7`](https://gith
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9610#issuecomment-156341479
The failed test is not related, I'm merging this into master, will create
another PR for other branches.
---
If your project is set up for it, you can reply to this emai
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9591#issuecomment-156341354
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9591#issuecomment-156341355
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9591#issuecomment-156341270
**[Test build #45821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45821/consoleFull)**
for PR 9591 at commit
[`7c9eb43`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9589#issuecomment-156341113
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9589#issuecomment-156341076
Merged build triggered.
---
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 h
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9288#issuecomment-156340809
@XuTingjun , I'm OK with the current way if finding the root cause is a
little bit complicated. Just need to add more comments why we have to change to
that way.
---
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/9589#issuecomment-156340093
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 thi
Github user carsonwang commented on the pull request:
https://github.com/apache/spark/pull/9297#issuecomment-156339821
Hi @vanzin, I updated the code to address your comments. Thank you!
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9589#issuecomment-156339391
Merged build finished. Test FAILed.
---
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/9589#issuecomment-156339357
**[Test build #45834 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45834/consoleFull)**
for PR 9589 at commit
[`6203bc7`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9589#issuecomment-156339392
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/5664#issuecomment-156339123
ok once jacky raise the PR, I will close this one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/9684#discussion_r44753574
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -538,6 +549,11 @@ private[yarn] class YarnAllocator(
if (exec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9297#issuecomment-156336778
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9297#issuecomment-156336780
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9297#issuecomment-156336683
**[Test build #45813 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45813/consoleFull)**
for PR 9297 at commit
[`fe5c165`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9610#issuecomment-156336017
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9610#issuecomment-156336014
Merged build finished. Test FAILed.
---
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/9610#issuecomment-156335873
**[Test build #45824 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45824/consoleFull)**
for PR 9610 at commit
[`71b12bf`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156335592
**[Test build #45837 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45837/consoleFull)**
for PR 9684 at commit
[`85d18d2`](https://gith
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/9594#discussion_r44752961
--- Diff:
examples/src/main/java/org/apache/spark/examples/ml/JavaMultilayerPerceptronClassifierExample.java
---
@@ -0,0 +1,74 @@
+/*
+ * Licensed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-156333984
**[Test build #45836 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45836/consoleFull)**
for PR 9390 at commit
[`65b3d16`](https://gith
Github user yanboliang closed the pull request at:
https://github.com/apache/spark/pull/9682
---
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/9651#issuecomment-156332601
**[Test build #45838 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45838/consoleFull)**
for PR 9651 at commit
[`240bcf3`](https://gith
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/9682#issuecomment-156332581
I think we should keep the ```DecisionTreeExample```, so closing this PR.
Thanks for your comments. @mengxr
---
If your project is set up for it, you can reply to t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156332449
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156332437
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9651#issuecomment-156332440
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9684#issuecomment-156332450
Merged build started.
---
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/9658#issuecomment-156332394
**[Test build #45835 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45835/consoleFull)**
for PR 9658 at commit
[`d17a2db`](https://gith
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/9684
[SPARK-11718][Yarn][Core]Fix explicitly killing executor dies silently issue
Currently if dynamic allocation is enabled, explicitly killing executor
will not get response, so the executor metadata
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9589#issuecomment-156331403
**[Test build #45834 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45834/consoleFull)**
for PR 9589 at commit
[`6203bc7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9320#issuecomment-156331018
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9320#issuecomment-156331014
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
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9680#issuecomment-156331258
I think 9366 is about computing corr or cov matrix whereas this is
computing corr between two columns. They seem to be useful in their own ways.
Also this is already
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-156330945
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156330974
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9390#issuecomment-156330975
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9658#issuecomment-156330934
Merged build triggered.
---
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9320#issuecomment-156330726
**[Test build #45832 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45832/consoleFull)**
for PR 9320 at commit
[`128eb70`](https://git
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/9651#discussion_r44752326
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -519,13 +526,33 @@ abstract class HadoopFsRelation
private[sql](mayb
1 - 100 of 1159 matches
Mail list logo
