Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135648633
@sun-rui I'll take a look at this tomorrow
---
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/8433#issuecomment-135648501
What's the meaning of param and field?
The scala documentation doesn't really say anything:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135655318
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135655321
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/6297#issuecomment-135655316
[Test build #41730 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41730/console)
for PR 6297 at commit
Github user noel-smith commented on the pull request:
https://github.com/apache/spark/pull/8399#issuecomment-135655500
That would be great - I've just messaged him. If there are any other
changes you need to get this into 1.5 I'll get them in ASAP today.
---
If your project is set
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38174902
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/local/FilterNodeSuite.scala
---
@@ -0,0 +1,41 @@
+/*
+* Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135664316
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8476#issuecomment-135664293
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135664287
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8476#issuecomment-135664315
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
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/8420#issuecomment-135664504
Sorry, I missed the Github notification. LGTM. The Scala REPL does the same
thing. Probably the ancient version of jline that was used before didn't
perform event
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8399#issuecomment-135656766
No, this LGTM. I'll merge this with branch-1.5 and master now. Thanks
very much!
---
If your project is set up for it, you can reply to this email and have your
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38175042
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/local/FilterNodeSuite.scala
---
@@ -0,0 +1,41 @@
+/*
+* Licensed to the Apache
Github user skyluc commented on the pull request:
https://github.com/apache/spark/pull/8433#issuecomment-135661207
It indicates on which of the elements generated for the class parameter to
apply the annotation.
There are 4 possible elements generated for a class parameter: the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135664705
[Test build #41735 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41735/consoleFull)
for PR 8343 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135664712
[Test build #41736 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41736/consoleFull)
for PR 8484 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135663625
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135663634
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
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135663528
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8455
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8218#issuecomment-135643130
Looks alright to me - would be good if @aarondav takes a look too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8455#issuecomment-135643024
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8498#discussion_r38176683
--- Diff: docs/mllib-migration-guides.md ---
@@ -7,6 +7,25 @@ description: MLlib migration guides from before Spark
SPARK_VERSION_SHORT
The
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8495#issuecomment-135656017
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/8495#issuecomment-135655957
[Test build #41724 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41724/console)
for PR 8495 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135657157
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8497#issuecomment-135657150
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/8492#issuecomment-135657152
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8399
---
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 dharmeshkakadia opened a pull request:
https://github.com/apache/spark/pull/8497
typo in comment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dharmeshkakadia/spark patch-2
Alternatively you can review and apply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135657175
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8498#issuecomment-135663172
[Test build #41734 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41734/consoleFull)
for PR 8498 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8495
---
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/8455#issuecomment-135643023
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 user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8455#issuecomment-135642972
[Test build #41729 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41729/console)
for PR 8455 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8218#discussion_r38173030
--- Diff:
network/common/src/main/java/org/apache/spark/network/client/TransportClient.java
---
@@ -70,6 +70,7 @@
private final Channel channel;
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8218#discussion_r38173055
--- Diff:
network/common/src/main/java/org/apache/spark/network/client/TransportClient.java
---
@@ -85,6 +86,25 @@ public SocketAddress getSocketAddress() {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135647373
[Test build #41723 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41723/console)
for PR 8458 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135647454
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/8458#issuecomment-135647453
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 user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135654582
[Test build #1701 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1701/console)
for PR 8492 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8496#issuecomment-135655198
[Test build #41731 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41731/consoleFull)
for PR 8496 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135654368
[Test build #41730 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41730/consoleFull)
for PR 6297 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135657968
[Test build #41733 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41733/consoleFull)
for PR 8492 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38175373
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/local/FilterNodeSuite.scala
---
@@ -0,0 +1,41 @@
+/*
+* Licensed to the Apache
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/8498
[SPARK-9671] [MLLIB] re-org user guide and add migration guide
This PR updates the MLlib user guide and adds migration guide for 1.4-1.5.
* merge migration guide for `spark.mllib` and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8498#issuecomment-135662135
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8498#issuecomment-135662156
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
Github user watermen commented on the pull request:
https://github.com/apache/spark/pull/8420#issuecomment-135648272
LGTM @dragos
---
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 cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135655783
Hi @viirya , thanks for looking into this!
The reason for this extra copy is that we iterate the array twice:
calculate elements data size and copy elements
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/8496#issuecomment-135655886
cc @davis @viirya
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135657176
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
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/8496
[SPARK-10065][SQL] avoid the extra copy when generate unsafe array
The reason for this extra copy is that we iterate the array elements twice:
one for calculate size, one for write to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8496#issuecomment-135653469
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8496#issuecomment-135653522
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8495#issuecomment-135656016
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 user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8484#discussion_r38177238
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/GenerateUnsafeProjection.scala
---
@@ -323,6 +309,7 @@ object
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135650454
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135650541
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/8484#discussion_r38174176
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/GenerateUnsafeProjection.scala
---
@@ -323,6 +309,7 @@ object
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38175256
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/local/UnionNode.scala ---
@@ -0,0 +1,75 @@
+/*
+* Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135657532
[Test build #41732 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41732/consoleFull)
for PR 6297 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135658488
[Test build #41727 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41727/console)
for PR 8492 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135658527
Test FAILed.
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/8492#issuecomment-135658526
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8487#issuecomment-135668992
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8500#issuecomment-135668988
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8501#issuecomment-135668985
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/8500#issuecomment-135669004
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8487#issuecomment-135669129
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8487#issuecomment-135681880
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/8487#issuecomment-135681877
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 user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8497
---
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/6297#issuecomment-135693383
[Test build #41732 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41732/console)
for PR 6297 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8499#issuecomment-135723505
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/8499#issuecomment-135723410
[Test build #41738 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41738/console)
for PR 8499 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8499#issuecomment-135723504
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 user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8498#issuecomment-135735710
[Test build #41734 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41734/console)
for PR 8498 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8498#issuecomment-135735979
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/8498#issuecomment-135735975
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 user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8506#issuecomment-135745326
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 josiahsams opened a pull request:
https://github.com/apache/spark/pull/8506
[SPARK-10172][core]Fix for HistoryServer webUI mess up during sorting
This pull request is to address the JIRA SPARK-10172 (History Server web UI
gets messed up when sorting on any column).
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8476#issuecomment-135666371
Test FAILed.
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/8476#issuecomment-135666370
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135667676
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 user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135667717
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 user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135667613
[Test build #41726 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41726/console)
for PR 7878 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135667719
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/8343#issuecomment-135667678
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8275#issuecomment-135672199
I backported this PR to branch-1.5 to fix 1.5 Jenkins build failures.
Didn't merge this PR to branch-1.5 before because it introduced new feature
after branch-1.5
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8489
---
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/8485#issuecomment-135705308
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8485#issuecomment-135705261
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8485#issuecomment-135709399
[Test build #41742 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41742/consoleFull)
for PR 8485 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8504#issuecomment-135722122
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
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8455#issuecomment-135665306
Thank you for merging it!
---
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/8493#issuecomment-135683072
[Test build #1702 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1702/consoleFull)
for PR 8493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135711841
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/8492#issuecomment-135711152
[Test build #41733 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41733/console)
for PR 8492 at commit
1 - 100 of 513 matches
Mail list logo
