Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14098
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62413/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14098
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/14098
**[Test build #62413 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62413/consoleFull)**
for PR 14098 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14090
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/14090
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62411/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14090
**[Test build #62411 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62411/consoleFull)**
for PR 14090 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14173
@felixcheung Just to confirm, based on discussion in SPARK-16508 is this
change good to merge ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14177
So I just tried the setup where I only have `enableHiveMetastore=F` for the
test case we are uncommenting and the `sparkR.session.stop` added to the other
test files as in this PR. That seems to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14098
**[Test build #62413 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62413/consoleFull)**
for PR 14098 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13894
**[Test build #62412 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62412/consoleFull)**
for PR 13894 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13894
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62412/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13894
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 does not have this feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13894
**[Test build #62412 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62412/consoleFull)**
for PR 13894 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14179
@krishnakalyan3 We don't need to modify the message. You can keep the
original message and just split it across two lines with something like the
`paste` function used in
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
@felixcheung @shivaram I am not sure if the warning message is clear
enough. I did the best I could with character limit of 100. I am not sure which
SparkR unit tests fail from the logs
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14221
---
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 issue:
https://github.com/apache/spark/pull/14090
**[Test build #62411 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62411/consoleFull)**
for PR 14090 at commit
Github user NarineK commented on the issue:
https://github.com/apache/spark/pull/14090
Thanks, I've generated the docs with your suggested way @shivaram, but I'm
not sure if I see the same thing as you.
I still see some '{% highlight r %}' and some formatting issues in general.
I
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14221
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14227
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/14223#discussion_r71071399
--- Diff: core/src/main/scala/org/apache/spark/util/Clock.scala ---
@@ -17,11 +17,21 @@
package org.apache.spark.util
+import
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14223#discussion_r71071394
--- Diff: core/src/main/scala/org/apache/spark/util/Clock.scala ---
@@ -17,11 +17,21 @@
package org.apache.spark.util
+import
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14227
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/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62410/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62410 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62410/consoleFull)**
for PR 14179 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62410 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62410/consoleFull)**
for PR 14179 at commit
Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/14219
Order of the indices in SparseVector potentially affects many other BLAS
operations. Perhaps we should have it in a more general/reusable pattern if we
do want to impose the validation.
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Hi, @rxin and @gatorsmile .
While I'm investigating `SQLBuilder` and building more exhaustive
testcases, I found that `SQLBuilder` seems to be **not exhaustive currently**.
It's not
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62409 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62409/consoleFull)**
for PR 14179 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14179
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62409/
Test FAILed.
---
Github user krishnakalyan3 commented on the issue:
https://github.com/apache/spark/pull/14179
@felixcheung my local unit test still fail, anyway thanks for the
clarification.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14179
**[Test build #62409 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62409/consoleFull)**
for PR 14179 at commit
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/14112#discussion_r71068992
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/LDA.scala ---
@@ -728,16 +755,40 @@ object DistributedLDAModel extends
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/14112#discussion_r71068982
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/LDA.scala ---
@@ -566,26 +565,54 @@ object LocalLDAModel extends
MLReadable[LocalLDAModel] {
Github user wuxianxingkong commented on a diff in the pull request:
https://github.com/apache/spark/pull/14191#discussion_r71067943
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -1376,4 +1376,62 @@ class SparkSqlAstBuilder(conf:
Github user wuxianxingkong commented on a diff in the pull request:
https://github.com/apache/spark/pull/14191#discussion_r71067768
--- Diff:
sql/catalyst/src/main/antlr4/org/apache/spark/sql/catalyst/parser/SqlBase.g4 ---
@@ -338,7 +338,7 @@ querySpecification
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14233
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 project does not have this
GitHub user rubenjanssen opened a pull request:
https://github.com/apache/spark/pull/14233
added a python example for chisq selector in mllib
## What changes were proposed in this pull request?
I added a python example for the chi sq selector in mllib. This one was
missing
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14136
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62408/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14136
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 does not have this feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14136
**[Test build #62408 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62408/consoleFull)**
for PR 14136 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14136
**[Test build #62408 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62408/consoleFull)**
for PR 14136 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14136
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62407/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14136
**[Test build #62407 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62407/consoleFull)**
for PR 14136 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14136
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 does not have this feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14136
**[Test build #62407 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62407/consoleFull)**
for PR 14136 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14150
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62406/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14150
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/14150
**[Test build #62406 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62406/consoleFull)**
for PR 14150 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14102
Sorry for pinging here and there.. @yhuai @liancheng
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14232#discussion_r71064096
--- Diff:
common/network-shuffle/src/main/java/org/apache/spark/network/shuffle/protocol/BlockTransferMessage.java
---
@@ -35,6 +35,9 @@
* shuffle
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14124
Could you take a look please @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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14117
Gentle ping @davies @liancheng
---
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 f7753 commented on a diff in the pull request:
https://github.com/apache/spark/pull/14232#discussion_r71064072
--- Diff:
common/network-shuffle/src/main/java/org/apache/spark/network/shuffle/protocol/BlockTransferMessage.java
---
@@ -35,6 +35,9 @@
* shuffle
Github user zasdfgbnm commented on a diff in the pull request:
https://github.com/apache/spark/pull/14231#discussion_r71063901
--- Diff: bin/spark-class ---
@@ -65,24 +65,25 @@ fi
# characters that would be otherwise interpreted by the shell. Read that
in a while loop,
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14232#discussion_r71063864
--- Diff:
common/network-shuffle/src/main/java/org/apache/spark/network/shuffle/protocol/BlockTransferMessage.java
---
@@ -35,6 +35,9 @@
* shuffle
Github user zasdfgbnm commented on a diff in the pull request:
https://github.com/apache/spark/pull/14231#discussion_r71063792
--- Diff: bin/spark-class ---
@@ -65,24 +65,25 @@ fi
# characters that would be otherwise interpreted by the shell. Read that
in a while loop,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14232
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 project does not have this
GitHub user f7753 opened a pull request:
https://github.com/apache/spark/pull/14232
[SPARK-16587] The annotation for the abstract Class 'BlockTransferMessage'
missing several kind of messages.
**# What changes were proposed in this pull request?**
Currently, the Messages used
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14231#discussion_r71063629
--- Diff: bin/spark-class ---
@@ -65,24 +65,25 @@ fi
# characters that would be otherwise interpreted by the shell. Read that
in a while loop,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14231
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 project does not have this
GitHub user zasdfgbnm opened a pull request:
https://github.com/apache/spark/pull/14231
[SPARK-16586] Change the way the exit code of launcher is handled to avoid
problem when launcher fails
## What changes were proposed in this pull request?
In the spark-class shell
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14150
**[Test build #62406 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62406/consoleFull)**
for PR 14150 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14098
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14098
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62405/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14098
**[Test build #62405 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62405/consoleFull)**
for PR 14098 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14098
**[Test build #62405 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62405/consoleFull)**
for PR 14098 at commit
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/14098
Not completed. Please hold on for review.
---
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 issue:
https://github.com/apache/spark/pull/14230
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62404/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14230
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/14230
**[Test build #62404 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62404/consoleFull)**
for PR 14230 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Ah, I'm investigating various places. There is several unclear parts to be
checked more.
Please abandon this PR today and go to bed. :)
---
If your project is set up for it, you can
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/12601
Thanks for pinging. Will take a look soon!
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14132
@rxin Sure
---
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14132#discussion_r71062028
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/SubstituteHintsSuite.scala
---
@@ -0,0 +1,208 @@
+/*
+ * Licensed to the
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14132
@gatorsmile let me know when you think this is ready.
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/11754#discussion_r71061953
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/SQLQuerySuite.scala
---
@@ -1776,4 +1776,33 @@ class SQLQuerySuite extends QueryTest
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14169
@jameszhouyi / adrian-wang / @chenghao-intel
related to this pull request, we want to have a native implementation for
ScriptTransform that does not depend on Hive's serdes. Can you let me
101 - 180 of 180 matches
Mail list logo
