Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9917#issuecomment-159086472
**[Test build #46557 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46557/consoleFull)**
for PR 9917 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-159088227
Sweet, thanks. 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
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/9603#issuecomment-159088257
Beyond that, the message is actually somewhat misleading. The "Stopping"
message occurs in `stop()`, which is responsible for stopping the
messageScheduler,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159091950
**[Test build #46556 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46556/consoleFull)**
for PR 9141 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159092083
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 BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159093878
No problem @jkbradley, I think this is good to go now
---
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 pull request:
https://github.com/apache/spark/pull/9919#issuecomment-159095679
**[Test build #46560 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46560/consoleFull)**
for PR 9919 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9853
---
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 dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9524#discussion_r45668289
--- Diff: mllib/pom.xml ---
@@ -125,6 +125,10 @@
org.apache.spark
spark-test-tags_${scala.binary.version}
+
+
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9524#discussion_r45669204
--- Diff: mllib/src/main/scala/org/apache/spark/ml/tree/codeGenerator.scala
---
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159085374
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/8610#issuecomment-159085218
**[Test build #46549 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46549/consoleFull)**
for PR 8610 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9917#issuecomment-159085929
/cc @rxin @zsxwing
While this problem also exists in 1.6, I didn't make this patch with the
intent of putting it there. If there's a desire to fix this in 1.6,
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-159087618
@vanzin, I've updated this patch to introduce a
`SPARK_VERSIONS_SUITE_IVY_PATH` environment variable which can be used to
configure a fixed directory instead of a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9613#issuecomment-159088695
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9613#issuecomment-159088540
**[Test build #46544 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46544/consoleFull)**
for PR 9613 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9793#issuecomment-159090248
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/9793#issuecomment-159090250
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-159091594
Reviewing now
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9427#issuecomment-159091597
@davies, I've updated this to address your comment; PTAL.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9598#issuecomment-159091586
looks good, perhaps reuse `predictionColName` and `labelColName`, instead
of `$(predictionCol)` and `$(labelCol)`, but it is minor
---
If your project is set up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159092086
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/9141#issuecomment-159092215
**[Test build #46555 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46555/consoleFull)**
for PR 9141 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/9919
[SPARK-11933][SQL] Rename mapGroup -> mapGroups and flatMapGroup ->
flatMapGroups.
Based on feedback from Matei, this is more consistent with mapPartitions in
Spark.
Also addresses some of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159092353
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 HyukjinKwon closed the pull request at:
https://github.com/apache/spark/pull/9763
---
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
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/9763#issuecomment-159095287
Oh. Right. Thanks!
Closing this.
---
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 mbautin commented on the pull request:
https://github.com/apache/spark/pull/9308#issuecomment-159099184
@rxin updated -- sorry for the delay.
---
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
GitHub user jliwork opened a pull request:
https://github.com/apache/spark/pull/9920
[SPARK-11569] [ML] Fix StringIndexer to handle null value properly
I was having some problem with rebase on
https://github.com/apache/spark/pull/9709, so I had to close that PR and
creating a new
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9141#issuecomment-159087888
**[Test build #46555 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46555/consoleFull)**
for PR 9141 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-159088942
**[Test build #46558 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46558/consoleFull)**
for PR 9624 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9918#issuecomment-159088830
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/9613#issuecomment-159088696
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/9793#issuecomment-159090033
**[Test build #46547 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46547/consoleFull)**
for PR 9793 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9427#issuecomment-159094315
[Test build #46559 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46559/consoleFull)
for PR 9427 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5622#issuecomment-159096459
**[Test build #46561 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46561/consoleFull)**
for PR 5622 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/9921
[SPARK-11934] [SQL] Adding joinType into joinWith
Except inner join, maybe the other join types are also useful when users
are using the joinWith function. Thus, added the joinType into the
Github user jliwork closed the pull request at:
https://github.com/apache/spark/pull/9709
---
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 jliwork commented on the pull request:
https://github.com/apache/spark/pull/9709#issuecomment-159098271
@dragos thanks for pointing it out. i am having some problem with rebase
and will close this PR.
---
If your project is set up for it, you can reply to this email and
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-159077566
Merging to master.
---
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 vanzin closed the pull request at:
https://github.com/apache/spark/pull/9530
---
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 utkarsh2012 commented on the pull request:
https://github.com/apache/spark/pull/8375#issuecomment-159078940
@saurfang Do you plan to merge this or you are waiting for @silasdavis's
changes?
---
If your project is set up for it, you can reply to this email and have your
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9860#issuecomment-159077637
Are you sure that we want this feature? Isn't this better handled by the
user via one of the many browser extensions for auto-refresh?
I feel like this would
Github user xguo27 commented on the pull request:
https://github.com/apache/spark/pull/9603#issuecomment-159079918
@andrewor14 What is your take on Jacek's comment? I don't think it's a bad
idea to make it more consistent with a matching log message. Please let me
know. Thx!
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9397#issuecomment-159081795
**[Test build #46554 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46554/consoleFull)**
for PR 9397 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9308#issuecomment-159101436
**[Test build #46563 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46563/consoleFull)**
for PR 9308 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5622#issuecomment-159145470
**[Test build #46571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46571/consoleFull)**
for PR 5622 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5622#issuecomment-159145524
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/5622#issuecomment-159145523
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/9909#issuecomment-159145911
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/9924#issuecomment-159147862
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/9917#issuecomment-159151618
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/9909#issuecomment-159145840
**[Test build #46577 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46577/consoleFull)**
for PR 9909 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9909#issuecomment-159145910
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/9924#issuecomment-159147801
**[Test build #46579 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46579/consoleFull)**
for PR 9924 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9924#issuecomment-159147861
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5622#issuecomment-159149102
If anything, this seemed to make thing slower. Closing for now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user JoshRosen closed the pull request at:
https://github.com/apache/spark/pull/5622
---
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/7753#issuecomment-159150999
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/7753#issuecomment-159150934
**[Test build #46576 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46576/consoleFull)**
for PR 7753 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-159150997
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/9917#issuecomment-159151566
**[Test build #46582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46582/consoleFull)**
for PR 9917 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9917#issuecomment-159151619
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9793#discussion_r45698452
--- Diff:
core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java
---
@@ -489,10 +495,6 @@ public void loadNext() throws
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9793#discussion_r45698964
--- Diff:
core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java
---
@@ -489,10 +495,6 @@ public void loadNext() throws
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9793#discussion_r45699105
--- Diff:
core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java
---
@@ -489,10 +495,6 @@ public void loadNext() throws
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9860#issuecomment-159157786
I "mimic" what we have on Jenkins for instance. I understand your points
guys. I just thought it's a convenient feature for users ;)
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9919#issuecomment-159158329
**[Test build #2099 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2099/consoleFull)**
for PR 9919 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9308#issuecomment-159159471
LGTM except a minor code style comments.
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9308#discussion_r45699604
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -1997,4 +1997,35 @@ class SQLQuerySuite extends QueryTest with
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9921#discussion_r45699792
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
---
@@ -412,7 +418,7 @@ class DatasetSuite extends QueryTest with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9840#issuecomment-159163316
**[Test build #46583 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46583/consoleFull)**
for PR 9840 at commit
GitHub user jkbradley opened a pull request:
https://github.com/apache/spark/pull/9927
[SPARK-11521] [ML] [DOC] Document that Logistic, Linear Regression
summaries ignore weight col
Doc for 1.6 that the summaries mostly ignore the weight column.
To be corrected for 1.7
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9919#issuecomment-159164011
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
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/9921#discussion_r45699959
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
---
@@ -412,7 +418,7 @@ class DatasetSuite extends QueryTest with
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9844#discussion_r45700102
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -610,9 +610,9 @@ class Analyzer(
*/
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-159164089
> Do you mean a LDAModel.load(path) which can load both local and
distributed LDAModel? We can create a jira.
Yes, that's what I had in mind. That way, most
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9924#issuecomment-159165834
I've merged this. Thanks.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9919
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9924
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9844#discussion_r45700402
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -661,7 +666,9 @@ class Analyzer(
val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9927#issuecomment-159168803
**[Test build #46584 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46584/consoleFull)**
for PR 9927 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9921#discussion_r45700482
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
---
@@ -412,7 +418,7 @@ class DatasetSuite extends QueryTest with
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9308#issuecomment-159167719
I'm going to merge this. The style thing is good to have, but probably
doesn't worth another roundtrip.
---
If your project is set up for it, you can reply to this email
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9308
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-159170379
LGTM. @hhbyyh Thanks for the updates! Is there anything left to do? If
not, can you please remove the "WIP" label? I can then merge it.
---
If your project is
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/9921#discussion_r45701047
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DatasetSuite.scala
---
@@ -412,7 +418,7 @@ class DatasetSuite extends QueryTest with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9921#issuecomment-159171315
**[Test build #46585 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46585/consoleFull)**
for PR 9921 at commit
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/9844#discussion_r45701500
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -661,7 +666,9 @@ class Analyzer(
val
Github user hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/9894#issuecomment-159171948
@jkbradley removed. Thanks.
---
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 jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9860#issuecomment-159172624
So, what do we do about this ?
First, let me go back to the checkbox (probably better IMHO in term of UI).
@JoshRosen I agree that using pushed async update
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9860#issuecomment-159172833
Rebase and back on the checkbox (instead of the button).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9844#discussion_r45702258
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -661,7 +666,9 @@ class Analyzer(
val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9816#issuecomment-159104877
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/9816#issuecomment-159104875
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 radekg commented on a diff in the pull request:
https://github.com/apache/spark/pull/9608#discussion_r45681436
--- Diff: core/src/main/scala/org/apache/spark/HttpFileServer.scala ---
@@ -42,10 +42,11 @@ private[spark] class HttpFileServer(
fileDir.mkdir()
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/9923
[SPARK-11563] [core] [repl] Use RpcEnv to transfer REPL-generated classes.
This avoids bringing up yet another HTTP server on the driver, and
instead reuses the file server already managed by the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9909#issuecomment-159113367
**[Test build #46568 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46568/consoleFull)**
for PR 9909 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9894#discussion_r45683880
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/LDA.scala ---
@@ -486,6 +487,61 @@ class LocalLDAModel private[ml] (
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9894#discussion_r45683892
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/LDA.scala ---
@@ -593,7 +686,8 @@ class DistributedLDAModel private[ml] (
@Since("1.6.0")
201 - 300 of 556 matches
Mail list logo
