Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-146380219
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/8953#issuecomment-146380220
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-146385212
Sure, looking at the logisticregression impl it seems that it currently
uses transform, but it doesn't do handle the case where the preidction col is
set to "", so I
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7788#issuecomment-146385308
@chenghao-intel, do you want to file a new JIRA to track only the partial
aggregation enhancements for Hive UDAF?
---
If your project is set up for it, you can reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-146385074
[Test build #43369 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43369/consoleFull)
for PR 8564 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9018#issuecomment-146387420
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 neil-rubens opened a pull request:
https://github.com/apache/spark/pull/9018
added option for specifying AWS credential profile
# Need
Utilizing AWS profiles is considered best practice:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146391277
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8918#issuecomment-146391749
[Test build #43374 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43374/consoleFull)
for PR 8918 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8880#issuecomment-146393548
[Test build #43375 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43375/consoleFull)
for PR 8880 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146393688
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146393660
[Test build #43365 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43365/console)
for PR 8988 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146393689
Test FAILed.
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/9015#issuecomment-146400251
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/9015#issuecomment-146400181
[Test build #43364 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43364/console)
for PR 9015 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9015#issuecomment-146400254
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/9021
[SPARK-10987] [yarn] Work around for netty rpc disconnection event.
In YARN client mode, when the AM connects to the driver, it may be the case
that the driver never needs to send a message back
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9021#issuecomment-146403614
/cc @zsxwing
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9016#discussion_r41474659
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeMapData.java
---
@@ -65,6 +65,22 @@ public UnsafeArrayData
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9009#issuecomment-146376151
LGTM
Ping @mengxr FYI. Also, which Spark versions are we patching?
---
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/9016#issuecomment-146376857
[Test build #43362 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43362/consoleFull)
for PR 9016 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8953#issuecomment-146379948
Test FAILed.
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/8988#issuecomment-146379997
[Test build #43365 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43365/consoleFull)
for PR 8988 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8953#issuecomment-146380034
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146380098
Yeah, I will.
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-146384581
LGTM, merging with 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9017#issuecomment-146388663
[Test build #43371 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43371/console)
for PR 9017 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-146388505
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 KaiXinXiaoLei closed the pull request at:
https://github.com/apache/spark/pull/8668
---
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 marmbrus opened a pull request:
https://github.com/apache/spark/pull/9019
[SPARK-10993] [SQL] Inital code generated encoder for product types
This PR is a first cut at code generating an encoder that takes a Scala
`Product` type and converts it directly into the
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9019#discussion_r41469930
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -91,7 +328,6 @@ trait ScalaReflection {
case t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9019#issuecomment-146393923
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/9019#issuecomment-146393911
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 sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/8962#discussion_r41470551
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1873,3 +1872,30 @@ setMethod("as.data.frame",
collect(x)
}
)
+
+#'
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7417#discussion_r41473252
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -274,12 +275,30 @@ private[sql] abstract class
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/9021#issuecomment-146420692
LGTM.
This though worries me that there are other similar bugs lurking in the
background. I would expect the new RPC to behave exactly like the old one
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9022#issuecomment-146421665
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/9022#issuecomment-146421664
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/9023#issuecomment-146424986
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 sun-rui opened a pull request:
https://github.com/apache/spark/pull/9023
[SPARK-10996][SPARKR] Implement sampleBy() in DataFrameStatFunctions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sun-rui/spark SPARK-10996
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9015#issuecomment-146369573
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/8988#issuecomment-146372265
[Test build #43361 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43361/consoleFull)
for PR 8988 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146379693
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/8988#issuecomment-146379704
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-146382752
Once this is merged (or now), can you please make an analogous JIRA for the
LogisticRegressionSummary? Thanks!
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146381878
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/8990#issuecomment-146381892
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-146382111
LGTM except for that style issue
---
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/8564#issuecomment-146384823
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8214
---
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/9017#issuecomment-146388686
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/8564#issuecomment-146388506
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-146390416
Yeah @tgravescs I'm running in yarn client mode. I'm sure that
`HDFS_DELEGATION_TOKEN token 2339 for spark` is the original token gained by
the driver. But I don't
Github user SaintBacchus closed the pull request at:
https://github.com/apache/spark/pull/8867
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8931#discussion_r41468737
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/metric/SQLMetrics.scala
---
@@ -35,6 +36,12 @@ private[sql] abstract class SQLMetric[R
Github user SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/8895#issuecomment-146390491
@liancheng Can you take a look at this small change?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9020#issuecomment-146395870
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/8953#issuecomment-146399283
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/8953#issuecomment-146399185
[Test build #43366 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43366/console)
for PR 8953 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8953#issuecomment-146399281
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/9023#issuecomment-146425647
[Test build #43382 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43382/consoleFull)
for PR 9023 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9015#issuecomment-146369559
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9015#issuecomment-146369470
/cc @yhuai for review.
---
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/9015#issuecomment-146378615
[Test build #43363 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43363/consoleFull)
for PR 9015 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8988#discussion_r41465749
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFilters.scala
---
@@ -282,33 +277,4 @@ private[sql] object
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9018#issuecomment-146387648
I think that this is a duplicate of #8696. Therefore, I'd recommend closing
this and bumping that other PR.
---
If your project is set up for it, you can reply to
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/7788#issuecomment-146387642
Yes @JoshRosen I've just created the issue
https://issues.apache.org/jira/browse/SPARK-10992, it will be great if you
assign this issue to me. :)
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8988#issuecomment-146391278
Test FAILed.
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/8988#issuecomment-146391252
[Test build #43361 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43361/console)
for PR 8988 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9019#issuecomment-146397989
Test FAILed.
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/9019#issuecomment-146397969
[Test build #43376 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43376/console)
for PR 9019 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9019#issuecomment-146397983
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 sun-rui commented on the pull request:
https://github.com/apache/spark/pull/8962#issuecomment-146399058
@rerngvit, could you rebase it to the latest master? As I moved stats
functions to a new R file stats.R in https://github.com/apache/spark/pull/8869
---
If your
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/8857#issuecomment-146399070
Hi @vanzin , @sryza any opinion on this PR? Thanks a lot.
---
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/9015#issuecomment-146399027
[Test build #43363 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43363/console)
for PR 9015 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9015#issuecomment-146399121
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/9015#issuecomment-146399120
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/9019#issuecomment-146404752
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/9019#issuecomment-146404765
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/9022#issuecomment-146407066
[Test build #43379 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43379/consoleFull)
for PR 9022 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146414313
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/7410#issuecomment-146414306
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/8880#issuecomment-146415843
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/8880#issuecomment-146415751
[Test build #43375 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43375/console)
for PR 8880 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9021#issuecomment-146420921
> This though worries me that there are other similar bugs lurking in the
background.
I'm sure there are. Any code that relies on the disconnection even may be
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8990#issuecomment-146420903
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/8990#issuecomment-146420914
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/7410#issuecomment-146426024
[Test build #43380 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43380/console)
for PR 7410 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-146425893
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/8942#issuecomment-146425872
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 SaintBacchus commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-146425804
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146427660
[Test build #43384 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43384/consoleFull)
for PR 7410 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8942#issuecomment-146427385
[Test build #43383 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43383/consoleFull)
for PR 8942 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146427371
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/9023#issuecomment-146428347
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/9023#issuecomment-146428350
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/9023#issuecomment-146428102
[Test build #43382 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43382/console)
for PR 9023 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-146427600
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/7410#issuecomment-146427585
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/7410#issuecomment-146426062
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
401 - 500 of 719 matches
Mail list logo
