Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58315661
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21449/consoleFull)
for PR 2529 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2682#issuecomment-58315769
Great, let's take it for a spin.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58315840
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2682
---
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/1616#issuecomment-58315865
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21447/consoleFull)
for PR 1616 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-58315866
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1685#issuecomment-58316202
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2689#issuecomment-58316342
This PR should point to SPARK-3420, I guess. We should leave SPARK-3412
open and close SPARK-3420 instead.
@JoshRosen
---
If your project is set up for it, you
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58316539
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1685#issuecomment-58316638
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21450/consoleFull)
for PR 1685 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58316998
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21451/consoleFull)
for PR 2529 at commit
GitHub user Ishiihara opened a pull request:
https://github.com/apache/spark/pull/2706
[SQL][Doc] Keep Spark SQL README.md up to date
@marmbrus
Update README.md to be consistent with Spark 1.1
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58318815
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/2529#issuecomment-58318810
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21449/consoleFull)
for PR 2529 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58319419
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/2706#issuecomment-58319420
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/2529#issuecomment-58319412
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21451/consoleFull)
for PR 2529 at commit
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2673#issuecomment-58319574
@vanzin yeah I agree - I think it was just sort of a red herring based on
the example in @ScrapCodes description. AFAIK this is totally unrelated to
Hadoop.
---
If
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58320520
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58320856
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21453/consoleFull)
for PR 2529 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2667#issuecomment-58320921
@srowen Ranking metrics are different from multiclass metrics. In general,
multiclass metrics do not consider the ordering of the predictions, but just
hits and misses,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1685#issuecomment-58322010
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21450/consoleFull)
for PR 1685 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1685#issuecomment-58322014
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/2707
[SPARK-3844][UI] Truncate appName in WebUI if it is too long
Truncate appName in WebUI if it is too long.
You can merge this pull request into a Git repository by running:
$ git pull
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2700#issuecomment-58323685
That doesn't look good. I think it is still nice to put the full set of
parameters in the WebUI, which is easier to check than the logs.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2707#issuecomment-58324074
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21454/consoleFull)
for PR 2707 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-58324547
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21455/consoleFull)
for PR 2388 at commit
GitHub user chouqin opened a pull request:
https://github.com/apache/spark/pull/2708
[SPARK-3158][MLLIB]Avoid 1 extra aggregation for DecisionTree training
Currently, the implementation does one unnecessary aggregation step. The
aggregation step for level L (to choose splits) gives
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2708#issuecomment-58325016
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21456/consoleFull)
for PR 2708 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2529#issuecomment-58325117
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/2529#issuecomment-58325112
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21453/consoleFull)
for PR 2529 at commit
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2520#discussion_r18570229
--- Diff: project/SparkBuild.scala ---
@@ -170,6 +178,24 @@ object SparkBuild extends PomBuild {
}
+object YARNCommon {
+ lazy
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2520#discussion_r18570223
--- Diff: project/SparkBuild.scala ---
@@ -170,6 +178,24 @@ object SparkBuild extends PomBuild {
}
+object YARNCommon {
+ lazy
GitHub user dbtsai opened a pull request:
https://github.com/apache/spark/pull/2709
Minor change in the comment of spark-defaults.conf.template
spark-defaults.conf is used in spark-shell as well, and this PR added this
into the comment.
You can merge this pull request into a Git
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2520#issuecomment-58328853
I did not check up on maven part, it looks okay. Apart from two comments
above, LGTM.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2570#issuecomment-58329046
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21458/consoleFull)
for PR 2570 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2709#issuecomment-58329045
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21457/consoleFull)
for PR 2709 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2707#issuecomment-58330380
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21454/consoleFull)
for PR 2707 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2707#issuecomment-58330386
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/2708#issuecomment-58330730
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/2708#issuecomment-58330725
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21456/consoleFull)
for PR 2708 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-58330999
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21455/consoleFull)
for PR 2388 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-58331009
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/2675#issuecomment-58333659
@scwf Jenkins still fails... Actually I just realized that
`HiveThriftServer2Suite` calls `start-thriftserver.sh` to start a separate
server process, and the log level
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2570#issuecomment-58334350
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/2570#issuecomment-58334343
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21458/consoleFull)
for PR 2570 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2667#issuecomment-58334664
@mengxr Yes I understand these metrics. Precision / recall are binary
classifier metrics at heart (but not nDCG for example). Precision@k needs
ranking. That's why
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2612#issuecomment-58335548
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21459/consoleFull)
for PR 2612 at commit
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2520#discussion_r18572940
--- Diff: project/SparkBuild.scala ---
@@ -170,6 +178,24 @@ object SparkBuild extends PomBuild {
}
+object YARNCommon {
+ lazy val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2709#issuecomment-58336192
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21457/consoleFull)
for PR 2709 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2709#issuecomment-58336202
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/2542#issuecomment-58338302
I tried this on hive:
CREATE TABLE t1(x INT);
CREATE TABLE t2(a STRUCTx: INT, k INT);
SELECT a.x FROM t1 a JOIN t2 b;
And hive can
Github user tianyi commented on the pull request:
https://github.com/apache/spark/pull/2542#issuecomment-58338634
@cloud-fan I had create a test case named test ambiguousReferences
resolved as hive , the case is almost the same as yours.
---
If your project is set up for it, you can
Github user tianyi commented on the pull request:
https://github.com/apache/spark/pull/2542#issuecomment-58339330
I think we should follow hive syntax as much as possible, which could save
lots of work when people move their application form hive to spark, @marmbrus
what's your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2708#issuecomment-58339521
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21460/consoleFull)
for PR 2708 at commit
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2520#discussion_r18574479
--- Diff: project/SparkBuild.scala ---
@@ -170,6 +178,24 @@ object SparkBuild extends PomBuild {
}
+object YARNCommon {
+ lazy
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2520#discussion_r18575095
--- Diff: project/SparkBuild.scala ---
@@ -170,6 +178,24 @@ object SparkBuild extends PomBuild {
}
+object YARNCommon {
+ lazy val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2612#issuecomment-58341737
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21459/consoleFull)
for PR 2612 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2612#issuecomment-58341742
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/2520#discussion_r18575772
--- Diff: project/SparkBuild.scala ---
@@ -170,6 +178,24 @@ object SparkBuild extends PomBuild {
}
+object YARNCommon {
+ lazy val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2708#issuecomment-58345233
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21460/consoleFull)
for PR 2708 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2708#issuecomment-58345239
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user ravipesala opened a pull request:
https://github.com/apache/spark/pull/2710
[SPARK-3814][SQL] Bitwise does not work in Hive
Currently there is no support of Bitwise in Spark HiveQl and Spark SQL as
well. So this PR support the same.
Author : ravipesala
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2710#issuecomment-58348032
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/2706#issuecomment-58350942
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/286/consoleFull)
for PR 2706 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2698#issuecomment-58353197
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21461/consoleFull)
for PR 2698 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2675#issuecomment-58353194
I also realized that. But i think there is some unkown reason here, i moved
```
// HACK: Hive is too noisy by default.
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/2475#discussion_r18580229
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -254,6 +254,8 @@ private[sql] abstract class SparkStrategies
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2671#issuecomment-58354129
we will fix it in #2675
---
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 scwf closed the pull request at:
https://github.com/apache/spark/pull/2671
---
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/2612#issuecomment-58354515
I added lint-scripts for checking style of scripts.
The script checks following things.
* EOL
* extra spaces before EOL
* tabs
* multibyte
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2675#issuecomment-58356235
Wow, very very strange!!! If i add a print in the hack, then
HiveThriftServer2Suite success.
```
// HACK: Hive is too noisy by default.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2706#issuecomment-58356613
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/286/consoleFull)
for PR 2706 at commit
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/2711
[WIP][SPARK-1720][SPARK-1719] use LD_LIBRARY_PATH instead of
-Djava.library.path
This is another implementation about #1031
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/2711#issuecomment-58358351
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21462/consoleFull)
for PR 2711 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2698#issuecomment-58359162
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/2698#issuecomment-58359149
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21461/consoleFull)
for PR 2698 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2675#issuecomment-58359171
OK, I removed the log level hack from `TestHiveContext`, let's see what
happens.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2649#issuecomment-58359605
test failure is in streaming-flume, totally unrelated to this.
changes look good, thanks @vanzin
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2675#issuecomment-58359794
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21463/consoleFull)
for PR 2675 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2650#issuecomment-58359865
changes look good.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/2649
---
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/2680#issuecomment-58360514
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21464/consoleFull)
for PR 2680 at commit
GitHub user james64 opened a pull request:
https://github.com/apache/spark/pull/2712
[SPARK-3121] Wrong implementation of implicit bytesWritableConverter
val path = ... //path to seq file with BytesWritable as type of both key
and value
val file =
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58361701
Jenkins, please start the 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2712#issuecomment-58361679
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 gvramana opened a pull request:
https://github.com/apache/spark/pull/2713
[SPARK-3559][SQL] Remove unnecessary columns from List of needed Column Ids
in Hive Conf
Author: Venkata Ramana G ramana.gollam...@huawei.com
You can merge this pull request into a Git repository
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2713#issuecomment-58364730
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/2612#issuecomment-58364698
Hm, can't git just manage this for us? Looks like you could tell git that
.cmd files are always text with Windows line endings with `.gitattributes`?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2711#issuecomment-58368014
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/2680#issuecomment-58368109
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21464/consoleFull)
for PR 2680 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2680#issuecomment-58368116
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user shijinkui closed the pull request at:
https://github.com/apache/spark/pull/2704
---
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 shijinkui opened a pull request:
https://github.com/apache/spark/pull/2714
[SPARK-3781] code Style format
code Style format, modify the third time :(
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shijinkui/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2704#issuecomment-58369606
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21465/consoleFull)
for PR 2704 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2704#issuecomment-58369787
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21465/consoleFull)
for PR 2704 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2704#issuecomment-58369791
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user shijinkui commented on the pull request:
https://github.com/apache/spark/pull/2704#issuecomment-58369964
@AmplabJenkins @andrewor14 review and run test again please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2714#issuecomment-58370041
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 shijinkui commented on the pull request:
https://github.com/apache/spark/pull/2714#issuecomment-58370144
@AmplabJenkins @andrewor14 review and run test again please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
1 - 100 of 449 matches
Mail list logo
