Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7564#issuecomment-125470413
[Test build #38677 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38677/consoleFull)
for PR 7564 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-125473405
[Test build #38662 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38662/console)
for PR 7580 at commit
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/7716#issuecomment-125477598
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
GitHub user fjiang6 opened a pull request:
https://github.com/apache/spark/pull/7722
[SPARK-3181][MLLIB]: Add Robust Regression Algorithm with Huber Estimator
Huber Robust Regression under spark/ml/regression
You can merge this pull request into a Git repository by running:
$
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/7721#issuecomment-125477614
@JoshRosen What's the context when we disable pylint checker? Should we
just remove the pylint totally?
---
If your project is set up for it, you can reply to this
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/7723
[SPARK-9402][SQL] Remove CodegenFallback from Abs / FormatNumber.
Both expressions already implement code generation.
You can merge this pull request into a Git repository by running:
$ git pull
Github user KaiXinXiaoLei commented on the pull request:
https://github.com/apache/spark/pull/7716#issuecomment-125477581
I think this patch has no association with the failed unit tests, please
retest.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-125477742
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/7721#issuecomment-125477864
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7697#discussion_r35619593
--- Diff:
examples/src/main/scala/org/apache/spark/examples/ml/KMeansExample.scala ---
@@ -0,0 +1,75 @@
+/*
+ * Licensed to the Apache Software
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/7724
[SPARK-9390][SQL][WIP] create a wrapper for array type
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark array-data
Github user avulanov commented on a diff in the pull request:
https://github.com/apache/spark/pull/3883#discussion_r35621506
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Pregel.scala ---
@@ -158,4 +159,91 @@ object Pregel extends Logging {
g
} // end of
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7655#discussion_r35622323
--- Diff: docs/mllib-evaluation-metrics.md ---
@@ -0,0 +1,1475 @@
+---
+layout: global
+title: Evaluation Metrics - MLlib
+displayTitle: a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5855#issuecomment-125506134
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5855#issuecomment-125525455
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/5855#issuecomment-125525176
[Test build #38693 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38693/console)
for PR 5855 at commit
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/7648#discussion_r35632711
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/rate/PIDRateEstimator.scala
---
@@ -0,0 +1,91 @@
+/*
+ * Licensed to the
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/7648#discussion_r35633081
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/rate/PIDRateEstimator.scala
---
@@ -0,0 +1,91 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7709#issuecomment-125542961
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/7720#issuecomment-125470087
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/7564#issuecomment-125470071
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7720#issuecomment-125471286
[Test build #1216 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1216/consoleFull)
for PR 7720 at commit
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/7708#issuecomment-125471931
@srowen how about changing all the `pre` to `{@code...}`?
---
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/7718#issuecomment-125472010
[Test build #38675 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38675/consoleFull)
for PR 7718 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7716#issuecomment-125477878
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/7716#issuecomment-125477904
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/7721#issuecomment-125477892
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/7722#issuecomment-125477849
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/7721#issuecomment-125477961
@davies, it was reverted while triaging a build break today. When the
PyLint download started failing builds today we initially misdiagnosed the
problem as an issue
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7723#issuecomment-125477891
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/7722#issuecomment-125477893
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/7723#issuecomment-125477841
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7716#issuecomment-125478062
[Test build #38684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38684/consoleFull)
for PR 7716 at commit
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/7697#issuecomment-125478031
@srowen I made examples in Scala and Java more simple. Could you review it?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7620#issuecomment-125482063
[Test build #38676 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38676/console)
for PR 7620 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7718#issuecomment-125487922
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/7718#issuecomment-125487819
[Test build #38668 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38668/console)
for PR 7718 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7642#issuecomment-125503293
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/6841#issuecomment-125514622
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/6841#issuecomment-125514595
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5855#issuecomment-125514490
[Test build #38693 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38693/consoleFull)
for PR 5855 at commit
Github user bolkedebruin commented on the pull request:
https://github.com/apache/spark/pull/7489#issuecomment-125537344
@harishreedharan all seems fine, history is properly linked for me. Would
be nice to have this in! +1 again :-)
---
If your project is set up for it, you can
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/7538#issuecomment-125545504
@feynmanliang thanks for your comments. I've addressed most of them (except
for the bins_
Is it agreed that the refactoring can be done in another PR?
---
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/7708#issuecomment-125476997
Alright. I'll create a JIRA to change all `pre` to `{@code...}`. I'll
send another PR later. Thanks!
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-125476903
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/7642#issuecomment-125476890
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/7642#issuecomment-125476863
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/7580#issuecomment-125476870
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/7711#issuecomment-125476613
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/7721#issuecomment-125476849
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/7721#issuecomment-125476888
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7697#discussion_r35619640
--- Diff:
examples/src/main/scala/org/apache/spark/examples/ml/KMeansExample.scala ---
@@ -0,0 +1,75 @@
+/*
+ * Licensed to the Apache Software
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7724#discussion_r35619651
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/GenericArrayData.scala
---
@@ -0,0 +1,127 @@
+package org.apache.spark.sql.types
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/7724#issuecomment-125479867
cc @rxin
---
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/7410#issuecomment-125485613
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/7718#issuecomment-125490055
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/7709#issuecomment-125504967
[Test build #38690 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38690/consoleFull)
for PR 7709 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5855#issuecomment-125506461
[Test build #38691 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38691/consoleFull)
for PR 5855 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7692#issuecomment-125507942
[Test build #38671 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38671/console)
for PR 7692 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7711#issuecomment-125507742
[Test build #38692 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38692/consoleFull)
for PR 7711 at commit
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/7538#discussion_r35629633
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -252,7 +254,13 @@ class LogisticRegression(override val
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/7600#discussion_r35629563
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/scheduler/RateControllerSuite.scala
---
@@ -0,0 +1,140 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7600#issuecomment-125539539
[Test build #38696 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38696/consoleFull)
for PR 7600 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7708#issuecomment-125475153
Hm, I do see many more uses of `{@code }` in the project than `pre` for
this purpose, which is good. It would be reasonable to fix, at least, all the
Java examples in
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7711#discussion_r35618667
--- Diff: dev/sparktestsupport/modules.py ---
@@ -29,7 +29,7 @@ class Module(object):
changed.
-def __init__(self, name,
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/7721
[SPARK-9835] [PySpark] fix install pylint
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davies/spark fix_install_pylint
Alternatively you can
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/7721#issuecomment-125475355
cc @yhuai
---
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/7722#issuecomment-125478247
[Test build #38683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38683/consoleFull)
for PR 7722 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7723#issuecomment-125478209
[Test build #38682 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38682/consoleFull)
for PR 7723 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-125488140
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/7580#issuecomment-125488188
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/7580#issuecomment-125488388
[Test build #134 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/134/consoleFull)
for PR 7580 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7712#issuecomment-125487989
[Test build #1214 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1214/console)
for PR 7712 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7655#discussion_r35622681
--- Diff: docs/mllib-evaluation-metrics.md ---
@@ -0,0 +1,1475 @@
+---
+layout: global
+title: Evaluation Metrics - MLlib
+displayTitle: a
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7655#discussion_r35622663
--- Diff: docs/mllib-evaluation-metrics.md ---
@@ -0,0 +1,1475 @@
+---
+layout: global
+title: Evaluation Metrics - MLlib
+displayTitle: a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7720#issuecomment-125496523
[Test build #1216 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1216/console)
for PR 7720 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5855#issuecomment-125507065
[Test build #38691 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38691/console)
for PR 5855 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7711#issuecomment-125507046
[Test build #38673 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38673/console)
for PR 7711 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7711#issuecomment-125507163
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/5855#issuecomment-125507068
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 does
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7716#issuecomment-125510974
[Test build #38684 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38684/console)
for PR 7716 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7716#issuecomment-125511044
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-125531025
ping @zhzhan @liancheng
---
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/7644#issuecomment-125537746
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7709#issuecomment-125542724
[Test build #135 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/135/console)
for PR 7709 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7708#issuecomment-125469263
Agree, this is not a fix. The modern way to write code javadoc is ...
```
{@code
val foo = ...
}
```
... but for consistency with other
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6644#issuecomment-125469705
[Test build #132 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/132/consoleFull)
for PR 6644 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6644#issuecomment-125469505
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/7564#issuecomment-125470118
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7707#discussion_r35618757
--- Diff: mllib/src/main/scala/org/apache/spark/ml/feature/RFormula.scala
---
@@ -78,13 +78,20 @@ class RFormula(override val uid: String) extends
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7707#discussion_r35618772
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/RFormulaParser.scala ---
@@ -0,0 +1,114 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7707#discussion_r35618774
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/RFormulaParser.scala ---
@@ -0,0 +1,114 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7707#discussion_r35618765
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/RFormulaParser.scala ---
@@ -0,0 +1,114 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7707#discussion_r35618780
--- Diff: mllib/src/main/scala/org/apache/spark/ml/r/SparkRWrappers.scala
---
@@ -32,8 +32,10 @@ private[r] object SparkRWrappers {
alpha: Double):
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7707#discussion_r35618777
--- Diff: mllib/src/main/scala/org/apache/spark/ml/r/SparkRWrappers.scala
---
@@ -32,8 +32,10 @@ private[r] object SparkRWrappers {
alpha: Double):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7721#issuecomment-125475844
Note that the code to actually run the PyLint checks is still commented
out, so you might want to revert that commit as part of this PR if you're
trying to re-enable
Github user ziky90 commented on the pull request:
https://github.com/apache/spark/pull/7596#issuecomment-125483602
@nchammas you are probably right that you can create IAM role and then use
this role to access the S3, but you can't use this when you have just AWS keys
and no IAM
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7410#issuecomment-125485482
[Test build #38661 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38661/console)
for PR 7410 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7711#issuecomment-125508112
I'm cool with merging this but let's make sure that we add a test
Kinesis item to our release checklists so that we run this test right before
packaging the release
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/7711#issuecomment-125508146
LGTM from my side, but I will wait for @JoshRosen to LGTM it since he is
most knowledgeable about this.
---
If your project is set up for it, you can reply to this email
1 - 100 of 1402 matches
Mail list logo
