Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8696
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user teramonagi commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-150072706
@JihongMA Thanks a lot Josh!!!
---
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 no
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149665535
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149665538
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149665527
**[Test build #44004 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44004/consoleFull)**
for PR 8696 at commit
[`5152fa4`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149665399
**[Test build #44004 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44004/consoleFull)**
for PR 8696 at commit
[`5152fa4`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149663843
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149663939
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149663191
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149654683
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149654689
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149650314
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149650285
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149649941
I'm going to run the Python style checker, then will merge this and update
the PR description myself. Thanks @teramonagi.
---
If your project is set up for it, you ca
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149649877
Jenkins, this is ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-149044450
LGTM. I would update the PR description though so when this gets merged in
the commit message has the rationale behind this change.
---
If your project is set up for i
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-148964651
This seems reasonable to me. Might be nice to have @nchammas take a quick
peek. If I don't hear otherwise, I'll merge this by Monday.
---
If your project is set up fo
Github user teramonagi commented on a diff in the pull request:
https://github.com/apache/spark/pull/8696#discussion_r42315781
--- Diff: ec2/spark_ec2.py ---
@@ -178,6 +178,9 @@ def parse_args():
"-i", "--identity-file",
help="SSH private key file to use fo
Github user teramonagi commented on a diff in the pull request:
https://github.com/apache/spark/pull/8696#discussion_r42315734
--- Diff: ec2/spark_ec2.py ---
@@ -1311,7 +1314,10 @@ def real_main():
sys.exit(1)
try:
-conn = ec2.connect_to_regio
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8696#discussion_r42314991
--- Diff: ec2/spark_ec2.py ---
@@ -1311,7 +1314,10 @@ def real_main():
sys.exit(1)
try:
-conn = ec2.connect_to_region
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8696#discussion_r42314994
--- Diff: ec2/spark_ec2.py ---
@@ -178,6 +178,9 @@ def parse_args():
"-i", "--identity-file",
help="SSH private key file to use for
Github user teramonagi commented on a diff in the pull request:
https://github.com/apache/spark/pull/8696#discussion_r42307104
--- Diff: ec2/spark_ec2.py ---
@@ -178,6 +178,9 @@ def parse_args():
"-i", "--identity-file",
help="SSH private key file to use fo
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8696#discussion_r42283806
--- Diff: ec2/spark_ec2.py ---
@@ -178,6 +178,9 @@ def parse_args():
"-i", "--identity-file",
help="SSH private key file to use for
Github user neil-rubens commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-146389503
+1
using AWS profile is considered to be best practice:
https://blogs.aws.amazon.com/security/post/Tx3D6U6WSFGOK2H/A-New-and-Standardized-Way-to-Manage-Crede
Github user teramonagi commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-139701773
@shivaram
"profiles" give us the way that you can specify the set of credentials you
want to use when you initialize a connection to AWS.
You can keep mu
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-139605764
@teramonagi Could you clarify what these profiles are meant to be ? Are
they IAM profiles or something else ?
cc @nchammas
---
If your project is set up for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8696#issuecomment-139190256
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pr
GitHub user teramonagi opened a pull request:
https://github.com/apache/spark/pull/8696
[SPARK-10532][EC2]Added --profile option to specify names profiles
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/teramonagi/spark SPARK-105
28 matches
Mail list logo
