Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7009#issuecomment-115124275
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/7009#issuecomment-115124260
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/7009#issuecomment-115124332
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-8567] [SQL] Add
Github user sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6990#issuecomment-115129184
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark]
[SPARK-8591][CORE]Block
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6946#issuecomment-115131090
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6946#issuecomment-115131160
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-8551][ML]
Elastic
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6946#issuecomment-115131105
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/6946#issuecomment-115131357
[Test build #35766 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35766/consoleFull)
for PR 6946 at commit
Github user FlytxtRnD commented on a diff in the pull request:
https://github.com/apache/spark/pull/6880#discussion_r33227267
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/DpMeansModel.scala ---
@@ -0,0 +1,149 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6946#issuecomment-115133949
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6998#issuecomment-115133888
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-8604] [SQL]
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6946#issuecomment-115133942
[Test build #35766 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35766/console)
for PR 6946 at commit
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/7008#issuecomment-115137638
You don't really need to reload the principal, but that is not a big deal.
This LGTM.
We probably should document that these parameters will not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6951#issuecomment-115137924
[Test build #35755 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35755/console)
for PR 6951 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7009#issuecomment-115140216
[Test build #35756 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35756/console)
for PR 7009 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7009#issuecomment-115140247
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 SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/7008#issuecomment-115148516
@harishreedharan You are right, the principal is all the same.
I considerred them as couple configurations, so I added it into the
list.:smile:
---
If your
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/7011
[Minor] [MLLib] rename some functions of PythonMLLibAPI
Keep the same naming conventions for PythonMLLibAPI.
Only the following three function is different from others
```scala
Github user sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6979#issuecomment-115149742
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-8587][PySpark]
Github user samos123 closed the pull request at:
https://github.com/apache/spark/pull/6979
---
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 prakashpc opened a pull request:
https://github.com/apache/spark/pull/7012
[SPARK-8603] [sparkR] In windows, Incorrect file seperator passed to Java
and Scripts from R
[SPARK-8603] [sparkR] In windows, Incorrect file seperator passed to Java
and Scripts from R
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6990#issuecomment-115128806
[Test build #35752 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35752/console)
for PR 6990 at commit
Github user sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/7005#issuecomment-115128152
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-8559][MLlib]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6990#issuecomment-115128936
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6972#issuecomment-115130412
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-5768] [Web UI]
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-115131501
[Test build #35754 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35754/console)
for PR 6672 at commit
Github user sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-115131648
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-115131543
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 sujkh85 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6880#discussion_r33227311
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/DpMeansModel.scala ---
@@ -0,0 +1,149 @@
+/*
+ * Licensed to the Apache Software
Github user sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/7008#issuecomment-115138300
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6951#issuecomment-115138079
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6951#issuecomment-115138411
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-8561][SQL]drop
Github user sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/7011#issuecomment-115149184
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [Minor] [MLLib] rename
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-115149489
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-115149573
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark]
[SPARK-4352][YARN][WIP]
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-115149458
[Test build #35764 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35764/console)
for PR 6394 at commit
Github user samos123 commented on the pull request:
https://github.com/apache/spark/pull/6979#issuecomment-115149642
Sure was just meant to express what kind of functionality I wanted.
Closing..
---
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/7011#issuecomment-115149583
[Test build #35767 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35767/consoleFull)
for PR 7011 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-115151455
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 jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-115151095
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/6394#issuecomment-115151557
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/7012#issuecomment-115152678
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ [spark] [SPARK-8603] [sparkR] In
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7012#issuecomment-115152812
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 vanzin opened a pull request:
https://github.com/apache/spark/pull/7026
[SPARK-8066, SPARK-8067] [hive] Add support for Hive 1.0, 1.1 and 1.2.
Allow HiveContext to connect to metastores of those versions; some new shims
had to be added to account for changing
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-115370523
hmm, now I am a little confused -- that test actually passes even without
your changes. Sorry this may have been my fault for suggesting a test in
`SparkContextSuite`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6996#issuecomment-115377042
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 sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/6796#issuecomment-115389042
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] [SPARK-4176][WIP]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7027#issuecomment-115391133
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/7001#issuecomment-115391144
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/7027#issuecomment-115391156
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/7001#issuecomment-115391843
[Test build #35810 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35810/consoleFull)
for PR 7001 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-115392655
[Test build #35811 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35811/consoleFull)
for PR 5423 at commit
Github user sujkh85 commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-115392584
NAVER - http://www.naver.com/
su...@naver.com ëê» ë³´ë´ì ë©ì¼ Re: [spark] SPARK-1537 [WiP]
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/6973#discussion_r33295521
--- Diff: core/src/main/scala/org/apache/spark/SparkEnv.scala ---
@@ -90,39 +92,47 @@ class SparkEnv (
private var driverTmpDirToDelete: Option[String]
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-115371870
None of the changes here are in `SparkContext`; the PR title is misleading,
since you're changing `SparkEnv`. What code path would cause `SparkEnv.stop()`
to be called
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6993#issuecomment-115377528
[Test build #35808 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35808/consoleFull)
for PR 6993 at commit
Github user paberline commented on the pull request:
https://github.com/apache/spark/pull/6995#issuecomment-115385801
I've received a suggestion this PR could be improved by using np.save(z) to
serialize the data and also preserve metadata about the NumPy array. I'm going
to
Github user JDrit commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-115393908
I wrote some benchmarking code for
[this](https://github.com/JDrit/avro_tests/tree/master) and the results are
recorded
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-115510094
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/6973#issuecomment-115509948
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/6973#issuecomment-115514708
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 rekhajoshm commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-115518782
thanks @vanzin for your comments.Updated the title.Other than SparkContext,
SparkEnv stop can be invoked from Scheduler, or if Driver commanded a shutdown,
Executor
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-115519300
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/7031#issuecomment-115519294
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/7031#issuecomment-115519286
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/7028#issuecomment-115526307
I've updated the code to move the injection to runJob. This means that
exceptions thrown from any path inside the DAGScheduler that fail the job will
now have their
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/7018#discussion_r33329879
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/CatalystTypeConverters.scala
---
@@ -363,6 +373,19 @@ object CatalystTypeConverters {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7028#issuecomment-115528136
[Test build #35824 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35824/consoleFull)
for PR 7028 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/7018#discussion_r0034
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/CatalystTypeConverters.scala
---
@@ -363,6 +373,19 @@ object CatalystTypeConverters {
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7018
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/7018#issuecomment-115528323
merged this into master, 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/7013#issuecomment-115530196
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6832#issuecomment-115530179
@srowen Did you get a chance to try the above out ? did it work ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7013#issuecomment-115529053
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/7013#issuecomment-115529155
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/6145#issuecomment-115511092
Found a test case for you...
https://issues.apache.org/jira/browse/SPARK-8588
And we should merge this fix into branch 1.4. cc @marmbrus @liancheng
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-115511157
[Test build #35821 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35821/consoleFull)
for PR 6973 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6934
---
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/6973#issuecomment-115514651
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 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7010#discussion_r33329025
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -72,98 +80,94 @@ class CodeGenContext {
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/7010#issuecomment-115517514
LGTM, merging this into master, 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7010
---
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/7031#issuecomment-115520565
[Test build #35823 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35823/consoleFull)
for PR 7031 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7031#issuecomment-115523681
[Test build #35823 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35823/console)
for PR 7031 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7031#issuecomment-115523723
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/7028#issuecomment-115526912
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 davies commented on the pull request:
https://github.com/apache/spark/pull/7018#issuecomment-115526785
LGTM, only one minor comment.
---
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/7028#issuecomment-115526839
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 commented on the pull request:
https://github.com/apache/spark/pull/7015#issuecomment-115528435
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 davies commented on the pull request:
https://github.com/apache/spark/pull/7013#issuecomment-115528525
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7015#issuecomment-115529032
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/7015#issuecomment-115529104
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 Lewuathe commented on the pull request:
https://github.com/apache/spark/pull/3636#issuecomment-115528883
@jkbradley I fixed unit tests. Could you check it, please? Thank you.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7015#issuecomment-115530243
[Test build #35825 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35825/consoleFull)
for PR 7015 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7005#issuecomment-115530380
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/7013#issuecomment-115530226
[Test build #35826 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35826/consoleFull)
for PR 7013 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7005#issuecomment-115530374
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 feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/7005#issuecomment-115530404
@mengxr Done, although it feels hacky.
* Is it okay to Scala `ClassTag` for initializing `FPGrowthModel` in Java
(see
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/6948#discussion_r0342
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/LDAModel.scala ---
@@ -184,6 +199,82 @@ class LocalLDAModel private[clustering] (
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/7027#discussion_r0365
--- Diff:
core/src/test/scala/org/apache/spark/deploy/SparkSubmitSuite.scala ---
@@ -548,6 +548,7 @@ object JarCreationTest extends Logging {
if
1 - 100 of 705 matches
Mail list logo
