Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148315153
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/9116#issuecomment-148321535
[Test build #43777 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43777/console)
for PR 9116 at commit
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/8884#issuecomment-148321601
I'll be able to merge this PR once the following two issues are addressed,
1) Have a test to verify that `L1` with normal will throw
`IllegalArugmentExcpetion`.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148321661
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/9055#issuecomment-148326620
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/9134#issuecomment-148326244
[Test build #43783 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43783/consoleFull)
for PR 9134 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-148326579
[Test build #43782 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43782/console)
for PR 9055 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-148326617
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/8923#issuecomment-148328330
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/9132
[SPARK-11126][SQL]Fix a memory leak in SQLListener._stageIdToStageMetrics
SQLListener adds all stage infos to `_stageIdToStageMetrics`, but only
removes stage infos belonging to SQL executions.
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9067#issuecomment-148296408
It's best to have a feature flag for this, in case it yields worse
performance. Eventually we should find a way to make this the default.
Can you do some
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9096#issuecomment-148297815
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/9096#issuecomment-148297838
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/9132#issuecomment-148298014
[Test build #43769 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43769/console)
for PR 9132 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9132#issuecomment-148298042
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 zjffdu opened a pull request:
https://github.com/apache/spark/pull/9134
[SPARK-11125] [SQL] Unreadable exception when running spark-sql withoâ¦
â¦ut building with -Phive-thriftserver and SPARK_PREPEND_CLASSES is set
This is the exception after this patch.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9055#issuecomment-148322379
[Test build #43782 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43782/consoleFull)
for PR 9055 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9131#issuecomment-148293771
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/9131#issuecomment-148293788
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 zhichao-li commented on the pull request:
https://github.com/apache/spark/pull/9096#issuecomment-148296512
Sounds good to have one. let me update the unit test.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9131#issuecomment-148296454
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/9131#issuecomment-148296453
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 zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9133#issuecomment-148297763
Sorry, it mixed with other commits, close it and make another PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user zjffdu closed the pull request at:
https://github.com/apache/spark/pull/9133
---
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/8923#issuecomment-148297821
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/8923#issuecomment-148297850
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 the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148306360
ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148306333
I wanna explain a bit more about this bug.
When we resolve sort ordering, we will use a [special
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148306268
[Test build #43775 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43775/consoleFull)
for PR 8652 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148310651
[Test build #43777 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43777/consoleFull)
for PR 9116 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148314559
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 dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/9123#issuecomment-148314200
@cloud-fan
Hi Wenchen, i have fixed the code based on your comments.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3677#issuecomment-148320850
[Test build #43781 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43781/consoleFull)
for PR 3677 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148320732
[Test build #43779 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43779/console)
for PR 8652 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148320814
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/9055#issuecomment-148320902
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/3677#issuecomment-148332965
[Test build #43781 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43781/console)
for PR 3677 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9130#discussion_r42088208
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -2153,6 +2153,9 @@ private[spark] object Utils extends Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9096#issuecomment-148298346
[Test build #43771 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43771/consoleFull)
for PR 9096 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9132#issuecomment-148298402
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/9132#issuecomment-148298386
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/8652#issuecomment-148320815
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/9055#issuecomment-148320889
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/9132#issuecomment-148323853
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/8923#issuecomment-148328074
[Test build #43772 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43772/console)
for PR 8923 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-148328328
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 the pull request:
https://github.com/apache/spark/pull/9067#issuecomment-148294059
@JoshRosen Thanks for explaining this patch. It does exactly what you said.
@rxin Do you think it is ok to add a configuration for turning on/off this
feature?
GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/9133
Spark 11125
This is the exception after this patch. Please help review
```
java.lang.NoClassDefFoundError: org/apache/hadoop/hive/cli/CliDriver
at
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-148297636
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 hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/8362#issuecomment-148305817
Another thought on hashing. The ClearSpring hash is a generic hash
function. We could used very specialized (hopefully fast) hashing functions,
because we know the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8652#issuecomment-148316845
[Test build #43779 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43779/consoleFull)
for PR 8652 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148316840
[Test build #43780 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43780/consoleFull)
for PR 8416 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148321658
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/9096#issuecomment-148325066
[Test build #43771 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43771/console)
for PR 9096 at commit
GitHub user brwe opened a pull request:
https://github.com/apache/spark/pull/9136
fix typo bellow -> below
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/brwe/spark typo-bellow
Alternatively you can review and apply these
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9118#discussion_r42135926
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -340,6 +340,14 @@ private[spark] class Client(
"for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148422385
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/9099#issuecomment-148424693
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/9099#issuecomment-148427409
[Test build #43788 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43788/consoleFull)
for PR 9099 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9136#issuecomment-148417063
Yes that's fine. Feel free to spell-check more of the docs and zap many
typos in one go, if there are more.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148424668
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 jodersky commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148438185
In general I agree with you, however since in this case some warnings (such
as deprecations) are not treated as fatal, the user gets a huge amount of
messages
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9130#discussion_r42144562
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -2153,6 +2153,9 @@ private[spark] object Utils extends Logging {
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9127#issuecomment-148439397
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148422334
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/9099#issuecomment-148430553
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/9099#issuecomment-148430550
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/9099#issuecomment-148431668
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148425914
[Test build #43787 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43787/consoleFull)
for PR 9099 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148430393
[Test build #43787 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43787/console)
for PR 9099 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148431674
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/9099#issuecomment-148431576
[Test build #43788 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43788/console)
for PR 9099 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9127#issuecomment-148440578
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/9127#issuecomment-148440512
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/9136#issuecomment-148388802
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/6841#issuecomment-148390637
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/9118#issuecomment-148409085
LGTM too, the tests seem to have passed as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/9061#issuecomment-148409592
lgtm
---
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 pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148390469
[Test build #43785 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43785/console)
for PR 6841 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148390634
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 zero323 commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148394778
It is there from 1.4.0.
Regarding tests I would prefer to wait until I get some clarification,
because right now I am not sure how to handle this.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8621#issuecomment-148502689
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/8621#issuecomment-148502712
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/8829#issuecomment-148508543
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8956#discussion_r42174368
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFilters.scala
---
@@ -48,6 +48,34 @@ private[sql] object
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8829#issuecomment-148508577
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8956#discussion_r42177215
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFilterSuite.scala
---
@@ -112,6 +112,11 @@ class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9072#issuecomment-148527610
[Test build #43813 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43813/consoleFull)
for PR 9072 at commit
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148550760
https://issues.apache.org/jira/browse/SPARK-11137
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9140#issuecomment-148559025
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/9140#issuecomment-148558893
[Test build #43814 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43814/console)
for PR 9140 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9140#issuecomment-148559021
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/9143#issuecomment-148561943
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 davies opened a pull request:
https://github.com/apache/spark/pull/9145
[WIP] Improve cache performance for primitive types
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davies/spark byte_buffer
Alternatively you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9144#issuecomment-148563763
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 mwws commented on a diff in the pull request:
https://github.com/apache/spark/pull/8760#discussion_r42199742
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/BlacklistTracker.scala ---
@@ -0,0 +1,243 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9143#issuecomment-148563602
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/9145#issuecomment-148565257
[Test build #43824 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43824/consoleFull)
for PR 9145 at commit
Github user zhichao-li commented on a diff in the pull request:
https://github.com/apache/spark/pull/9097#discussion_r42201471
--- Diff:
sql/hive/src/main/java/org/apache/spark/sql/hive/mapred/CombineSplitRecordReader.java
---
@@ -0,0 +1,128 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9145#issuecomment-148571238
[Test build #43824 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43824/console)
for PR 9145 at commit
101 - 200 of 603 matches
Mail list logo
