You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2010/12/24 01:19:45 UTC
[jira] Created: (WHIRR-176) Set AWS credentials in the local site
file for Hadoop S3 access
Set AWS credentials in the local site file for Hadoop S3 access
---------------------------------------------------------------
Key: WHIRR-176
URL: https://issues.apache.org/jira/browse/WHIRR-176
Project: Whirr
Issue Type: New Feature
Components: service/hadoop
Reporter: Tom White
We should set fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in the local generated config file so it is easy for users to use the s3n Hadoop filesystem. Ditto for the s3 properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-176) Set AWS credentials in the local site
file for Hadoop S3 access
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated WHIRR-176:
------------------------------
Fix Version/s: 0.3.0
Assignee: Lars George
Affects Version/s: 0.3.0
Status: Patch Available (was: Open)
> Set AWS credentials in the local site file for Hadoop S3 access
> ---------------------------------------------------------------
>
> Key: WHIRR-176
> URL: https://issues.apache.org/jira/browse/WHIRR-176
> Project: Whirr
> Issue Type: New Feature
> Components: service/hadoop
> Affects Versions: 0.3.0
> Reporter: Tom White
> Assignee: Lars George
> Fix For: 0.3.0
>
> Attachments: WHIRR-176.patch
>
>
> We should set fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in the local generated config file so it is easy for users to use the s3n Hadoop filesystem. Ditto for the s3 properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-176) Set AWS credentials in the local site
file for Hadoop S3 access
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated WHIRR-176:
------------------------------
Attachment: WHIRR-176.patch
Adds AWS credentials to local hadoop-site.xml when the provider is set to "ec2".
> Set AWS credentials in the local site file for Hadoop S3 access
> ---------------------------------------------------------------
>
> Key: WHIRR-176
> URL: https://issues.apache.org/jira/browse/WHIRR-176
> Project: Whirr
> Issue Type: New Feature
> Components: service/hadoop
> Reporter: Tom White
> Attachments: WHIRR-176.patch
>
>
> We should set fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in the local generated config file so it is easy for users to use the s3n Hadoop filesystem. Ditto for the s3 properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WHIRR-176) Set AWS credentials in the local site
file for Hadoop S3 access
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated WHIRR-176:
----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
+1
I just committed this. Thanks Lars!
> Set AWS credentials in the local site file for Hadoop S3 access
> ---------------------------------------------------------------
>
> Key: WHIRR-176
> URL: https://issues.apache.org/jira/browse/WHIRR-176
> Project: Whirr
> Issue Type: New Feature
> Components: service/hadoop
> Affects Versions: 0.3.0
> Reporter: Tom White
> Assignee: Lars George
> Fix For: 0.3.0
>
> Attachments: WHIRR-176.patch
>
>
> We should set fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in the local generated config file so it is easy for users to use the s3n Hadoop filesystem. Ditto for the s3 properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.