[ http://issues.apache.org/jira/browse/HADOOP-574?page=comments#action_12454753 ] Tom White commented on HADOOP-574: ----------------------------------
Thinking about this more perhaps the best thing would be to put the access key and secret access key into the configuration file (as implemented in the first two patches, the properties are fs.s3.awsAccessKeyId and fs.s3.awsSecretAccessKey), but keep the bucket name as a part of the URI: s3://bucket/. As an enhancement we might allow the keys to be specified in the URI (per Doug's original suggestion) if people wanted to put them there (escaped). These would take precedence over keys specified in the config file. > want FileSystem implementation for Amazon S3 > -------------------------------------------- > > Key: HADOOP-574 > URL: http://issues.apache.org/jira/browse/HADOOP-574 > Project: Hadoop > Issue Type: New Feature > Components: fs > Affects Versions: 0.9.0 > Reporter: Doug Cutting > Attachments: dependencies.zip, HADOOP-574-v2.patch, HADOOP-574.patch > > > An S3-based Hadoop FileSystem would make a great addition to Hadoop. > It would facillitate use of Hadoop on Amazon's EC2 computing grid, as > discussed here: > http://www.mail-archive.com/hadoop-user@lucene.apache.org/msg00318.html > This is related to HADOOP-571, which would make Hadoop's FileSystem > considerably easier to extend. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
