Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-112272958
[Test build #34965 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34965/console)
for PR 6504 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6834#issuecomment-112278720
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 markhamstra commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-112254025
Yes, @jerryshao, the idiom is a little clearer when the contents of the
Option are actually be used to produce a result other than Unit, but it's also
a little odd
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6834#issuecomment-112277854
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/6834#issuecomment-112277949
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/6762#issuecomment-112291731
[Test build #34971 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34971/consoleFull)
for PR 6762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112291662
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/6762#issuecomment-112291651
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/6834#issuecomment-112304047
[Test build #34970 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34970/console)
for PR 6834 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6834#issuecomment-112304147
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 carsonwang commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-112260070
Thanks for reviewing this, @vanzin . The code is updated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user carsonwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6827#discussion_r32487191
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/FsHistoryProviderSuite.scala
---
@@ -218,6 +223,18 @@ class FsHistoryProviderSuite extends
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/6339#issuecomment-112266368
@mengxr - should we put this in the parent class or maybe just add a trait
for transformers which are invertible?
---
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/6460#issuecomment-112270153
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/6460#issuecomment-112270163
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 suyanNone opened a pull request:
https://github.com/apache/spark/pull/6834
Only show 4096 bytes content for executor log instead all
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/suyanNone/spark small-display
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6804#issuecomment-112282692
[Test build #916 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/916/console)
for PR 6804 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6762#issuecomment-112284174
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/6762#issuecomment-112284158
[Test build #34966 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34966/console)
for PR 6762 at commit
Github user zhichao-li commented on the pull request:
https://github.com/apache/spark/pull/6822#issuecomment-112303316
cc @chenghao-intel
---
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 yanboliang commented on the pull request:
https://github.com/apache/spark/pull/6460#issuecomment-112258204
retest
---
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/6762#issuecomment-112259725
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/6762#issuecomment-112259713
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/6827#issuecomment-112278245
[Test build #34967 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34967/console)
for PR 6827 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-112278349
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/6834#issuecomment-112278709
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/6834#issuecomment-112283191
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/6835#issuecomment-112286482
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/6460#issuecomment-112291866
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/6460#issuecomment-112291848
[Test build #34968 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34968/console)
for PR 6460 at commit
GitHub user zhichao-li opened a pull request:
https://github.com/apache/spark/pull/6836
[SPARK-8206][SQL]Add function round [WIP]
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zhichao-li/spark round
Alternatively you can
Github user zhichao-li commented on the pull request:
https://github.com/apache/spark/pull/6836#issuecomment-112303194
cc @chenghao-intel
---
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 jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-112246206
Hi @markhamstra , I'm pretty sure about this style `o.map{ ... }.getOrElse{
... }`, but here we transfer nothing but only print some different logs, so
here using
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-112248944
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/6783#issuecomment-112249174
[Test build #34963 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34963/consoleFull)
for PR 6783 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-112248937
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 XuTingjun commented on a diff in the pull request:
https://github.com/apache/spark/pull/6817#discussion_r32484601
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -537,10 +537,19 @@ private[spark] class ExecutorAllocationManager(
Github user carsonwang commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-112258599
@vanzin SPARK-8275 is a different issue. What I wanted to fix in this PR is
to avoid showing an App ID like application_1432793609805_009_1.inprogress.
This is not a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-112258739
[Test build #34965 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34965/consoleFull)
for PR 6504 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-112258631
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/6504#issuecomment-112258642
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/6762#issuecomment-112260360
[Test build #34966 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34966/consoleFull)
for PR 6762 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/5208#issuecomment-112260579
@justmytwospence yes.
---
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/6827#issuecomment-112260564
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/6827#issuecomment-112260574
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/6827#issuecomment-112260668
[Test build #34967 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34967/consoleFull)
for PR 6827 at commit
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-112265729
So from running with a slightly larger scaling factor than I was initially
it seems all the approaches are pretty similar in terms of time usage.
origin:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-112266986
[Test build #34963 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34963/console)
for PR 6783 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6783#issuecomment-112267010
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/6779#issuecomment-112272667
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 yijieshen opened a pull request:
https://github.com/apache/spark/pull/6835
[SPARK-8280][SPARK-8281][SQL]Handle NaN, null and Infinity in math
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yijieshen/spark
Github user shimingfei commented on the pull request:
https://github.com/apache/spark/pull/6702#issuecomment-112291544
@andrewor14 @aarondav
Can you take a look? Thanks!
---
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/6836#issuecomment-112303491
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/6836#issuecomment-112303476
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6827#discussion_r32437127
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -282,8 +282,12 @@ private[history] class FsHistoryProvider(conf:
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6774#issuecomment-112122962
Sounds like violent agreement. If there are no more comments I'll get this
merged.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112123063
[Test build #34946 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34946/consoleFull)
for PR 6831 at commit
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6817#issuecomment-112125769
HI @XuTingjun can you create a jira? It would be good to understand the
motivation for adding this
---
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/6831#issuecomment-112131491
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/6831#issuecomment-112131430
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 markmsmith commented on the pull request:
https://github.com/apache/spark/pull/6777#issuecomment-112132954
Sorry, my mistake, closing it now. 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
Github user markmsmith closed the pull request at:
https://github.com/apache/spark/pull/6777
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112132605
[Test build #34950 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34950/consoleFull)
for PR 6831 at commit
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6752#issuecomment-112134991
The other part that needs to get added is the user docs in
running-on-yarn.md -- I suppose that can wait till we agree on the approach.
---
If your project is set up
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/6205#discussion_r32442260
--- Diff: core/src/test/scala/org/apache/spark/rpc/RpcEnvSuite.scala ---
@@ -162,9 +163,15 @@ abstract class RpcEnvSuite extends SparkFunSuite with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6804#issuecomment-112158778
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/6804#issuecomment-112158820
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/6774#issuecomment-112159412
And as I said numerous times, whether to use env variables or something
else to propagate a secret has absolutely zero to do with whether you can
support per-app
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-112160908
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/6686#issuecomment-112160926
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/5694#issuecomment-112166730
[Test build #34956 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34956/consoleFull)
for PR 5694 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-112167513
[Test build #34956 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34956/console)
for PR 5694 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-112167521
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/5694#issuecomment-112171222
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/6831#issuecomment-112170874
[Test build #34951 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34951/console)
for PR 6831 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-112161079
[Test build #34954 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34954/consoleFull)
for PR 6686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112162597
[Test build #34950 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34950/console)
for PR 6831 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112162638
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/6752#issuecomment-112163696
I think our comments about user config crossed each other ... anyhow:
No, I was actually replying to you. :-) It's just that github doesn't
understand the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-112165147
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/5694#issuecomment-112169875
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/5694#issuecomment-112169804
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/6752#issuecomment-112171261
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/5694#issuecomment-112171219
[Test build #34957 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34957/console)
for PR 5694 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6752#issuecomment-112171301
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/6752#issuecomment-112172333
[Test build #34958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34958/consoleFull)
for PR 6752 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6816
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112153095
[Test build #34947 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34947/console)
for PR 6831 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112153143
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 acidghost commented on a diff in the pull request:
https://github.com/apache/spark/pull/6761#discussion_r32449001
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/NaiveBayes.scala ---
@@ -113,6 +106,55 @@ class NaiveBayesModel private[mllib] (
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6804#issuecomment-112159377
[Test build #34953 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34953/consoleFull)
for PR 6804 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112162297
[Test build #34949 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34949/console)
for PR 6831 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112162372
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/5694#issuecomment-112163559
[Test build #34955 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34955/consoleFull)
for PR 5694 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-112170845
[Test build #34957 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34957/consoleFull)
for PR 5694 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112170906
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6816#issuecomment-112173980
@rxin Created
[SPARK-8382](https://issues.apache.org/jira/browse/SPARK-8382) for better
analysis unit tests. @cloud-fan feel free to take a stab at that if you have
Github user acidghost commented on a diff in the pull request:
https://github.com/apache/spark/pull/6761#discussion_r32448418
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/NaiveBayes.scala ---
@@ -113,6 +106,55 @@ class NaiveBayesModel private[mllib] (
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6804#issuecomment-112156908
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 have
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6774#issuecomment-112163122
If stdin is a viable approach and we agree to use it for per-app secret
support now, it gives me justification to introduce appSecret in
ApplicationDescription and
201 - 300 of 482 matches
Mail list logo
