Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16146
**[Test build #70189 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70189/consoleFull)**
for PR 16146 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16146
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70189/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16146
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15915#discussion_r92611203
--- Diff:
core/src/test/scala/org/apache/spark/storage/MemoryStoreSuite.scala ---
@@ -60,7 +60,7 @@ class MemoryStoreSuite
SizeEstimator
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15915#discussion_r92611127
--- Diff:
core/src/main/scala/org/apache/spark/storage/memory/MemoryStore.scala ---
@@ -331,7 +331,15 @@ private[spark] class MemoryStore(
var
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15996
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/15996
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70188/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15996
**[Test build #70188 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70188/testReport)**
for PR 15996 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15996
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/15996
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70187/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15996
**[Test build #70187 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70187/testReport)**
for PR 15996 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15915
**[Test build #70191 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70191/testReport)**
for PR 15915 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
okay
---
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
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/15915
OK, I will give an update as soon as possible.
---
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 issue:
https://github.com/apache/spark/pull/16030
LGTM, pending jenkins. Can you also update the PR title and description?
thanks!
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r92600521
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2067,8 +2067,8 @@ class SparkContext(config: SparkConf) extends Logging
{
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16146
**[Test build #70189 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70189/consoleFull)**
for PR 16146 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16030
**[Test build #70190 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70190/testReport)**
for PR 16030 at commit
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16030#discussion_r92600244
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/HadoopFsRelation.scala
---
@@ -49,10 +51,16 @@ case class HadoopFsRelation(
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16146
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16030#discussion_r92599776
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/HadoopFsRelation.scala
---
@@ -49,10 +51,16 @@ case class HadoopFsRelation(
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15996#discussion_r92598769
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -363,48 +365,125 @@ final class DataFrameWriter[T] private[sql](ds:
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15996#discussion_r92597757
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -363,48 +365,125 @@ final class DataFrameWriter[T] private[sql](ds:
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15996#discussion_r92597284
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -363,48 +365,125 @@ final class DataFrameWriter[T] private[sql](ds:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15996
**[Test build #70188 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70188/testReport)**
for PR 15996 at commit
Github user Mironor commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r92595845
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2067,8 +2067,8 @@ class SparkContext(config: SparkConf) extends Logging
{
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15996
**[Test build #70187 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70187/testReport)**
for PR 15996 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16030
**[Test build #70186 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70186/testReport)**
for PR 16030 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16173
**[Test build #3499 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3499/testReport)**
for PR 16173 at commit
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16030#discussion_r92594503
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/HadoopFsRelation.scala
---
@@ -49,9 +49,12 @@ case class HadoopFsRelation(
Github user michalsenkyr commented on the issue:
https://github.com/apache/spark/pull/16157
Sorry for the delay. You are probably right that the partitioning is
primarily determined by data locality and that it is therefore appropriate in
some cases and shouldn't be worded such as to
Github user linbojin commented on the issue:
https://github.com/apache/spark/pull/16276
@srowen So any problems with my current implementation, i mean use
`implicit asTraversable: T => TraversableOnce[U]`. Because I refer to `flatten`
implementation in scala source code:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16289
**[Test build #3498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3498/testReport)**
for PR 16289 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16289
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70184/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16281
Yes, but we face bugs in third-party components all the time and work
around them or get them fixed. There is an unmentioned downside here too: not
getting bug fixes and improvements that don't
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16289
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/16289
**[Test build #70184 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70184/testReport)**
for PR 16289 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16281
Those issues with Parquet are specified for certain Parquet versions. If
upgrading Parquet can solve them, it can't justify the decision to fork
Parquet. To fork such project we need more
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16252
@srowen I am fine for that.
---
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
Github user kapilsingh5050 commented on the issue:
https://github.com/apache/spark/pull/16146
@cloud-fan The last test failure is because of following error:
"impossible to get artifacts when data has not been loaded. IvyNode =
org.scala-lang#scala-library;2.10.3"
for which
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16271#discussion_r92578668
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/lib/PageRank.scala
---
@@ -225,11 +225,11 @@ object PageRank extends Logging {
ctx =>
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16271#discussion_r92578753
--- Diff:
graphx/src/test/scala/org/apache/spark/graphx/lib/PageRankSuite.scala ---
@@ -70,10 +70,10 @@ class PageRankSuite extends SparkFunSuite with
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15915
You could also cap it at 16MB here. Or 128MB or whatever. That is unrelated
to introducing a new config.
It seems funny that setting to allow Int.MaxValue but map anything else to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16146
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70185/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16146
**[Test build #70185 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70185/consoleFull)**
for PR 16146 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16146
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 srowen commented on the issue:
https://github.com/apache/spark/pull/16276
Yes you're hitting a key point, that `flatten` only makes sense on an RDD
of `TraversableOnce`. I think we'd implement this in the way that
`DoubleRDDFunctions` adds operations for only RDDs of
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/15212
@mpjlu Sorry for late response, I just finished QA work for 2.1 and start
ordinary review. Could you resolve the merge conflicts first? I will take a
look tomorrow. Thanks.
---
If your project
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16146
**[Test build #70185 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70185/consoleFull)**
for PR 16146 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16173
**[Test build #3499 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3499/testReport)**
for PR 16173 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16157
OK, net-net I am OK merging this doc change even if it's not exactly what I
might write. It does contain useful additional detail that's accurate at the
moment.
---
If your project is set up for
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15018
If it's correct and faster, I tend to favor merging this. The code looks OK
to my understanding and passes existing tests.
---
If your project is set up for it, you can reply to this email and have
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/16279
Ok, thanks for the pointer. I do agree this is a non critical judgement
call .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16252
OK, do we have consensus to put the hasNext check back? before we ask
@wangyum to change again
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16295#discussion_r92570902
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -302,22 +302,19 @@ class KMeans @Since("1.5.0") (
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16281
One more example: https://github.com/apache/spark/pull/16106 This issue
degrades the performance.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16281
We keep hitting the issues in Parquet. Below is another example:
https://issues.apache.org/jira/browse/SPARK-18539
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16295
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 srowen commented on the issue:
https://github.com/apache/spark/pull/16281
Forking is a very bad thing, and only a last resort. We haven't properly
managed the fork of Hive yet, even. I don't hear specific bugs to fork around
here either. As such I can't see why this would
GitHub user ZakariaHili opened a pull request:
https://github.com/apache/spark/pull/16295
[SPARK-18356] [ML] KMeans should cache RDD before training
## What changes were proposed in this pull request?
According to request of Mr. Joseph Bradley , I did this update of my PR
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16289
**[Test build #70184 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70184/testReport)**
for PR 16289 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16289
**[Test build #3498 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3498/testReport)**
for PR 16289 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16289
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16286
I would vote for some logical grouping (instead of alphabetical ordering)
and keep the sections in the same order, but it is not very necessary.
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16290
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70181/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16290
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/16289
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/16294
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/16294
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70182/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16289
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70183/
Test FAILed.
---
401 - 470 of 470 matches
Mail list logo
