Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-114023080
[Test build #35436 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35436/consoleFull)
for PR 6647 at commit
[`d464641`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-114022836
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/6647#issuecomment-114022828
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 commented on the pull request:
https://github.com/apache/spark/pull/5707#issuecomment-114021371
@Lewuathe Thanks for iterating on this with me! Those should be the final
touches.
---
If your project is set up for it, you can reply to this email and have your
re
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/5707#discussion_r32908213
--- Diff: python/pyspark/mllib/util.py ---
@@ -169,6 +175,28 @@ def loadLabeledPoints(sc, path, minPartitions=None):
minPartitions = minPartitio
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/5707#discussion_r32908216
--- Diff: python/pyspark/mllib/util.py ---
@@ -169,6 +175,28 @@ def loadLabeledPoints(sc, path, minPartitions=None):
minPartitions = minPartitio
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/5707#discussion_r32908215
--- Diff: python/pyspark/mllib/util.py ---
@@ -169,6 +175,28 @@ def loadLabeledPoints(sc, path, minPartitions=None):
minPartitions = minPartitio
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5805#issuecomment-114021300
[Test build #35435 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35435/consoleFull)
for PR 5805 at commit
[`3d06806`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-114021183
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/6864#issuecomment-114021161
[Test build #35429 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35429/console)
for PR 6864 at commit
[`99a73ab`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5805#issuecomment-114021043
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/5805#issuecomment-114021028
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/6926#issuecomment-114020968
@jkbradley Thank you for reviewing it!
---
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 do
Github user jacek-lewandowski commented on the pull request:
https://github.com/apache/spark/pull/5805#issuecomment-114020441
@andrewor14 rebased
---
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/6864#discussion_r32907926
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/commands.scala ---
@@ -417,15 +428,14 @@ private[sql] class DefaultWriterContainer(
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6887#issuecomment-114018753
Yeah, I guess I'm OK either way. I figure the normal user won't care if
it's a strict n-gram but might be upset if a non-empty document produces an
all-zero feature v
Github user piaozhexiu commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-114018716
```
[error] Failed tests:
[error] org.apache.spark.sql.hive.ParquetDataSourceOnMetastoreSuite
[error] org.apache.spark.sql.hive.ParquetMetastoreSuit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6926#issuecomment-114017999
LGTM pending tests
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6931#issuecomment-114017820
@navis Thanks for the PR. Actually, I have committed the fix
(https://github.com/apache/spark/pull/6888) in master. The jira is still open
because the backport for 1.4 bra
Github user navis commented on the pull request:
https://github.com/apache/spark/pull/6810#issuecomment-114017606
@JoshRosen Sure, I'll review your patch first. 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 y
Github user navis commented on the pull request:
https://github.com/apache/spark/pull/6931#issuecomment-114016842
@marmbrus Could you review this, plz?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6931#issuecomment-114016814
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-114016671
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/6921#issuecomment-114016660
[Test build #35431 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35431/console)
for PR 6921 at commit
[`b87e107`](https://github.
GitHub user navis opened a pull request:
https://github.com/apache/spark/pull/6931
[SPARK-8420] [SQL] Inconsistent behavior with Dataframe Timestamp between
1.3.1 and 1.4.0
Havn't seen that the issue was fixed already. But It seemed it still has a
inconsistency problem on equals an
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6926#issuecomment-114016531
[Test build #35434 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35434/consoleFull)
for PR 6926 at commit
[`7cd0948`](https://gith
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-114016526
LGTM. Left two comments regarding adding comments/docs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6926#issuecomment-114016438
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/6926#issuecomment-114016420
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 viirya closed the pull request at:
https://github.com/apache/spark/pull/6929
---
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6864#discussion_r32907403
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/commands.scala ---
@@ -417,15 +428,14 @@ private[sql] class DefaultWriterContainer(
as
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/6926#issuecomment-114016250
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
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6864#discussion_r32907374
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/commands.scala ---
@@ -417,15 +428,14 @@ private[sql] class DefaultWriterContainer(
as
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6930#issuecomment-114014692
@SeekerResource Seems you accidentally created this pr. Can you close it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6928#issuecomment-114014345
Yeah I think that sounds reasonable. Tying this up with the
SparkSubmitSuite will be pretty messy. One easy way to do this is to just pull
out the code to construct the
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/6928#issuecomment-114014173
Well, since SparkSubmitt should ready be tested, could we just test the
param code gen?
---
If your project is set up for it, you can reply to this email and have your
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6928#discussion_r32906528
--- Diff: R/pkg/R/sparkR.R ---
@@ -81,6 +81,7 @@ sparkR.stop <- function() {
#' @param sparkExecutorEnv Named list of environment variables to be used
w
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-114011488
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/6647#issuecomment-114011451
[Test build #35432 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35432/console)
for PR 6647 at commit
[`be5ee2d`](https://github.
Github user sebastian-alfers commented on the pull request:
https://github.com/apache/spark/pull/6613#issuecomment-114010780
@yu-iskw sure, linked with the corresponding jira:
https://issues.apache.org/jira/browse/SPARK-7334
---
If your project is set up for it, you can reply to this
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/6903#discussion_r32906350
--- Diff:
repl/scala-2.11/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -98,875 +60,39 @@ class SparkILoop(in0: Option[BufferedReader],
pro
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114009881
[Test build #35433 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35433/consoleFull)
for PR 6914 at commit
[`9882915`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114009579
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/6914#issuecomment-114009585
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114009501
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 featur
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-114009420
[Test build #35432 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35432/consoleFull)
for PR 6647 at commit
[`be5ee2d`](https://gith
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6929#issuecomment-114009470
Merged. Can you close it? Thanks for the hotfix!
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6929#issuecomment-114009185
The mima failure seems not related to the change. I am merging it to fix
the 1.4 build.
---
If your project is set up for it, you can reply to this email and have your
re
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-114008939
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/6647#issuecomment-114008928
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/6921#issuecomment-114007763
[Test build #35431 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35431/consoleFull)
for PR 6921 at commit
[`b87e107`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-114007694
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/6921#issuecomment-114007704
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/6930#issuecomment-114006976
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 SeekerResource opened a pull request:
https://github.com/apache/spark/pull/6930
Branch 1.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/spark branch-1.4
Alternatively you can review and apply these changes
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6929#issuecomment-114006261
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/6929#issuecomment-114006230
[Test build #35430 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35430/consoleFull)
for PR 6929 at commit
[`b1aec53`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6877#issuecomment-114006133
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/6877#issuecomment-114006060
[Test build #35426 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35426/console)
for PR 6877 at commit
[`e582628`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6929#issuecomment-114001588
[Test build #35430 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35430/consoleFull)
for PR 6929 at commit
[`b1aec53`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6929#issuecomment-114000392
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/6929#issuecomment-114000325
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 viirya opened a pull request:
https://github.com/apache/spark/pull/6929
[HotFix] Hotfix branch-1.4 building by removing avgMetrics in
CrossValidatorSuite
Ref. #6905
ping @yhuai
You can merge this pull request into a Git repository by running:
$ git pull https
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113999842
[Test build #35429 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35429/consoleFull)
for PR 6864 at commit
[`99a73ab`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113999024
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/6864#issuecomment-113998951
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113998876
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113998119
**[Test build #35423 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35423/console)**
for PR 6864 at commit
[`99a73ab`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113998128
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 brkyvz commented on the pull request:
https://github.com/apache/spark/pull/6928#issuecomment-113997802
Hey @shivaram and @holdenk! I have a lot of package related utils
[here](https://github.com/apache/spark/blob/master/core/src/test/scala/org/apache/spark/deploy/IvyTestUti
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-113997483
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/6921#issuecomment-113997472
[Test build #35427 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35427/console)
for PR 6921 at commit
[`945a882`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113995859
[Test build #35428 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35428/console)
for PR 6685 at commit
[`21912dc`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113995870
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 nssalian commented on the pull request:
https://github.com/apache/spark/pull/6924#issuecomment-113995711
@mateiz made the changes. Not sure about the master yarn sentence.
Please let me know what do you think about it.
Thank you.
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113995160
[Test build #35428 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35428/consoleFull)
for PR 6685 at commit
[`21912dc`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113995011
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/6685#issuecomment-113995004
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/6918#issuecomment-113994649
[Test build #35422 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35422/console)
for PR 6918 at commit
[`855f9aa`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6918#issuecomment-113994663
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/6928#issuecomment-113992576
Thanks @holdenk -- Change looks pretty good. I just had some minor style
comments. BTW do you know if we re-use some test spark package to create a unit
test for this ?
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6928#discussion_r32903426
--- Diff: R/pkg/R/sparkR.R ---
@@ -81,6 +81,7 @@ sparkR.stop <- function() {
#' @param sparkExecutorEnv Named list of environment variables to be used
w
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6928#discussion_r32903405
--- Diff: R/pkg/R/client.R ---
@@ -51,7 +51,11 @@ launchBackend <- function(args, sparkHome, jars,
sparkSubmitOpts) {
jars <- paste("--jars", jars)
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6928#discussion_r32903397
--- Diff: R/pkg/R/sparkR.R ---
@@ -100,7 +101,8 @@ sparkR.init <- function(
sparkEnvir = list(),
sparkExecutorEnv = list(),
sparkJars = "
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-113990642
[Test build #35427 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35427/consoleFull)
for PR 6921 at commit
[`945a882`](https://gith
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6927#discussion_r32903263
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/LinearRegressionSuite.scala
---
@@ -78,6 +85,49 @@ class LinearRegressionSuite extends SparkFunS
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6927#discussion_r32903235
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/LinearRegressionSuite.scala
---
@@ -34,14 +35,20 @@ class LinearRegressionSuite extends SparkFun
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-113990502
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/6921#issuecomment-113990497
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-113990022
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
en
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6877#issuecomment-113989634
[Test build #35426 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35426/consoleFull)
for PR 6877 at commit
[`e582628`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6877#issuecomment-113989560
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/6877#issuecomment-113989558
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/6927#discussion_r32902999
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/LinearRegressionSuite.scala
---
@@ -34,14 +35,20 @@ class LinearRegressionSuite extends SparkFun
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6927#discussion_r32902975
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -133,7 +144,11 @@ class LinearRegression(override val uid: String)
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6927#discussion_r32902955
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -121,8 +131,9 @@ class LinearRegression(override val uid: String)
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/6927#discussion_r32902830
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -73,6 +74,15 @@ class LinearRegression(override val uid: String)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6927#issuecomment-113983058
[Test build #35421 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35421/console)
for PR 6927 at commit
[`f34971c`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6927#issuecomment-113983074
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6780#discussion_r32902049
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -106,12 +103,16 @@ case class InsertIntoHiveTable(
1 - 100 of 419 matches
Mail list logo
