Github user dusenberrymw commented on the pull request:
https://github.com/apache/spark/pull/6585#issuecomment-108137053
@rxin Sure thing, just added Python support for the `drop` with a `Column`
reference.
---
If your project is set up for it, you can reply to this email and have yo
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/6598
[SPARK-7558] Demarcate tests in unit-tests.log (1.4)
This includes the following commits:
original: 9eb222c
hotfix1: 8c99793
hotfix2: a4f2412
scalastyle check: 609c492
You ca
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6547
---
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 enab
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6547#issuecomment-108136412
master 1.4 thanks cheng
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108136414
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6493#issuecomment-108136348
OK, I re-merged this in 1.4 since the follow up fix for java 6 is up.
---
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/5915#issuecomment-108135793
[Test build #876 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/876/consoleFull)
for PR 5915 at commit
[`49b507b`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-108135039
[Test build #34029 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34029/consoleFull)
for PR 6504 at commit
[`d8616fd`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-108135052
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108134354
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108134344
[Test build #34030 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34030/consoleFull)
for PR 6591 at commit
[`e905f6d`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108134271
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 have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6592
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108134256
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108134093
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108134086
[Test build #34025 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34025/consoleFull)
for PR 6595 at commit
[`8ee7c7e`](https://git
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108134101
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 thi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108132692
[Test build #34033 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34033/consoleFull)
for PR 6576 at commit
[`e7ca406`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108132591
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108132605
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108132371
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108132359
[Test build #34024 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34024/consoleFull)
for PR 6592 at commit
[`1d89107`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108131340
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108131335
[Test build #34032 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34032/consoleFull)
for PR 6386 at commit
[`f35a16a`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108130994
[Test build #34032 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34032/consoleFull)
for PR 6386 at commit
[`f35a16a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108130909
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108130933
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108130718
[Test build #34027 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34027/consoleFull)
for PR 6576 at commit
[`6bb6d77`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108130730
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
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6386#discussion_r31581715
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/LogisticRegression.scala
---
@@ -363,4 +371,54 @@ class LogisticRegressionWithLBFGS
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5792#discussion_r31581618
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/FsHistoryProviderSuite.scala
---
@@ -335,6 +337,53 @@ class FsHistoryProviderSuite extends FunSu
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/5792#discussion_r31581433
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/FsHistoryProviderSuite.scala
---
@@ -335,6 +337,53 @@ class FsHistoryProviderSuite exte
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5792#discussion_r31581325
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -219,6 +221,67 @@ private[history] class FsHistoryProvider(conf:
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/5792#discussion_r31580887
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -219,6 +221,67 @@ private[history] class FsHistoryProvide
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6479#issuecomment-108125825
[Test build #874 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/874/consoleFull)
for PR 6479 at commit
[`f37c8c3`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108125497
[Test build #34019 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34019/consoleFull)
for PR 5841 at commit
[`2821481`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108125511
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
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6386#discussion_r31580761
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/LogisticRegression.scala
---
@@ -363,4 +371,54 @@ class LogisticRegressionWithLBFGS
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108124362
As long as this is aimed at 1.4.1 (not 1.4.0), should we design a better
fix? My suggestion would be to have PipelineStage include a Param specifying
whether to use i
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108122565
[Test build #34031 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34031/consoleFull)
for PR 5400 at commit
[`8ec2c5c`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108122303
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108122321
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 have
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6508#discussion_r31579551
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -443,9 +466,27 @@ private[spark] class ExecutorAllocationManager
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6593#issuecomment-108121991
[Test build #34022 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34022/consoleFull)
for PR 6593 at commit
[`b282241`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6593#issuecomment-108122006
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6594#issuecomment-108120373
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6594#issuecomment-108120331
[Test build #34021 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34021/consoleFull)
for PR 6594 at commit
[`9eee5aa`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5915#issuecomment-108119731
[Test build #876 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/876/consoleFull)
for PR 5915 at commit
[`49b507b`](https://githu
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6594#issuecomment-108119134
For save/load, I don't think that creating Java-friendly copies is a
problem. Will we have many different methods to copy?
This should have unit tests. I'm w
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108118075
[Test build #34030 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34030/consoleFull)
for PR 6591 at commit
[`e905f6d`](https://gith
Github user coderxiang commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-108118216
@jkbradley @dbtsai I removed the pipeline and `o.a.s.example` part in
@dbtsai's code so that the code example can be paste and run directly in
spark-shell. Please let
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6593#issuecomment-108117837
@pwendell I'll wait for @srowen to take a look before merging this -- I'll
also send a PR to github.com/pwendell/spark-utils before merging.
---
If your project is set
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6386#discussion_r31578786
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -100,8 +100,28 @@ class LogisticRegression(override val uid:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-108117578
[Test build #34029 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34029/consoleFull)
for PR 6504 at commit
[`d8616fd`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-108117482
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108117481
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6593#issuecomment-108117467
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6593#issuecomment-108117450
[Test build #34020 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34020/consoleFull)
for PR 6593 at commit
[`8f100a5`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-108117468
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108117466
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 h
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6386#discussion_r31578527
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -100,8 +100,28 @@ class LogisticRegression(override val uid:
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6562#issuecomment-108117188
Nevermind, I'll just wait until 1.4 is out so that I can then include it
for 1.4.1
---
If your project is set up for it, you can reply to this email and have your
rep
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6562#issuecomment-108117050
I'll merge this with 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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-108116822
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 pr
GitHub user eggsby opened a pull request:
https://github.com/apache/spark/pull/6597
[SPARK-7743] [SQL] Upgrading parquet version from incubator 1.6.0rc3
Resolves [SPARK-7743](https://issues.apache.org/jira/browse/SPARK-7743).
Trivial changes of versions, package names, as we
Github user dusenberrymw commented on the pull request:
https://github.com/apache/spark/pull/6540#issuecomment-108116098
@jkbradley Can you please review this PR?
---
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 pr
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6596#issuecomment-108115810
[Test build #34028 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34028/consoleFull)
for PR 6596 at commit
[`d3812f8`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6596#issuecomment-108115386
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6596#issuecomment-108115365
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 h
GitHub user jkbradley opened a pull request:
https://github.com/apache/spark/pull/6596
[SPARK-8053] [mllib] renamed scalingVector to scalingVec
I searched the Spark codebase for all occurrences of "scalingVector"
CC: @mengxr
You can merge this pull request into a Git repos
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6423#issuecomment-108114244
[Test build #34026 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34026/consoleFull)
for PR 6423 at commit
[`b70c945`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108113785
[Test build #34027 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34027/consoleFull)
for PR 6576 at commit
[`6bb6d77`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108113375
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6423#issuecomment-108113358
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6423#issuecomment-108113372
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6576#issuecomment-108113352
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5915#issuecomment-108113230
[Test build #875 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/875/consoleFull)
for PR 5915 at commit
[`49b507b`](https://gith
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6576#discussion_r31576746
--- Diff:
examples/src/main/scala/org/apache/spark/examples/ml/LogisticRegressionExample.scala
---
@@ -0,0 +1,160 @@
+/*
+ * Licensed to the Apache So
Github user harsha2010 commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108113064
@mengxr , yes, that works. 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 doe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108112580
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108112555
[Test build #34017 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34017/consoleFull)
for PR 5400 at commit
[`112c49e`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108109948
[Test build #34025 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34025/consoleFull)
for PR 6595 at commit
[`8ee7c7e`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108109413
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108109432
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6360#issuecomment-108108560
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108108615
[Test build #34024 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34024/consoleFull)
for PR 6592 at commit
[`1d89107`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6360#issuecomment-108108537
[Test build #34016 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34016/consoleFull)
for PR 6360 at commit
[`220358b`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108108495
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108108472
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 h
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108108161
We could add a debug flag (or debugLevel) in the future to control extra
columns. By default, users shouldn't see this column.
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108104373
[Test build #34023 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34023/consoleFull)
for PR 6595 at commit
[`e112394`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108104709
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108104702
[Test build #34023 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34023/consoleFull)
for PR 6595 at commit
[`e112394`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108104226
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108104204
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 h
Github user coderxiang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6576#discussion_r31573439
--- Diff:
examples/src/main/scala/org/apache/spark/examples/ml/LogisticRegressionExample.scala
---
@@ -0,0 +1,160 @@
+/*
+ * Licensed to the Apach
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/6595
[SPARK-8051] [MLLIB] make StringIndexerModel silent if input column does
not exist
This is just a workaround to a bigger problem. Some pipeline stages may not
be effective during prediction, and the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6562#issuecomment-108103752
[Test build #872 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/872/consoleFull)
for PR 6562 at commit
[`c16821b`](https://gith
Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/6205#issuecomment-108103617
Hi @squito,
Yeah that all makes sense and I think we are on the same page, so let me
put what we've been talking about in another commit and we can take another
Github user harsha2010 commented on the pull request:
https://github.com/apache/spark/pull/6592#issuecomment-108102305
+1 looks good. thanks @mengxr
I do have one question: does it make sense to promote this column which
actually stores the predictions of the underlying classifier
301 - 400 of 906 matches
Mail list logo
