Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-132711788
+1, looks good. go ahead and commit.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8134
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-132347459
@tgravescs I chose a slightly different name than you suggested, how does
that sound?
---
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/8134#issuecomment-132328545
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-132220380
changes lgtm. Only thing would be if we want to make some common config
name spark.yarn.access.* or other for everything access/token/security related.
@sryza
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-132272297
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/8134#issuecomment-132272344
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/8134#issuecomment-132275146
[Test build #41143 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41143/consoleFull)
for PR 8134 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-132328473
[Test build #41143 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41143/console)
for PR 8134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-132328547
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-131207621
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-131217902
I'm not against this just wondering what the use case is here? Did you
actually run into an issue?
---
If your project is set up for it, you can reply to this email
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-131220028
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-131222384
[Test build #40918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40918/consoleFull)
for PR 8134 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-131219607
Did you actually run into an issue?
Yes actually. Hive-on-Spark uses Spark to execute jobs, but not for
metastore access. The inherited configuration sometimes
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-131208405
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/8134#issuecomment-131208434
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/8134#issuecomment-131209735
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/8134#issuecomment-131209737
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/8134#issuecomment-131221317
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/8134#issuecomment-131221216
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/8134#issuecomment-131262278
[Test build #40918 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40918/console)
for PR 8134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-131262356
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/8134#issuecomment-131262358
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130852509
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130856138
[Test build #40808 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40808/consoleFull)
for PR 8134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130854533
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/8134#issuecomment-130903158
**[Test build #40808 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40808/console)**
for PR 8134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130903225
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/8134#issuecomment-130854600
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/8134#issuecomment-130831730
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/8134#issuecomment-130830304
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/8134#issuecomment-130830335
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/8134#issuecomment-130911194
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/8134#issuecomment-130961801
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/8134#issuecomment-130961761
**[Test build #40834 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40834/console)**
for PR 8134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130911242
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130909726
sigh. 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/8134#issuecomment-130913842
[Test build #40834 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40834/consoleFull)
for PR 8134 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130829388
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130466459
**[Test build #40654 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40654/console)**
for PR 8134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130466537
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/8134#issuecomment-130471250
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130471184
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130471231
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/8134#issuecomment-130472161
[Test build #40685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40685/consoleFull)
for PR 8134 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130506465
**[Test build #40685 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40685/console)**
for PR 8134 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130506520
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 vanzin opened a pull request:
https://github.com/apache/spark/pull/8134
[SPARK-9833] [yarn] Add options to disable delegation token retrieval.
This allows skipping the code that tries to talk to Hive and HBase to
fetch delegation tokens, in case that somehow
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8134#issuecomment-130418588
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/8134#issuecomment-130418607
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/8134#issuecomment-130420857
[Test build #40654 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40654/consoleFull)
for PR 8134 at commit
52 matches
Mail list logo
