You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2018/06/18 00:19:00 UTC
[jira] [Created] (DRILL-6511) Bootstrap S3 storage plugin is
misleading
Paul Rogers created DRILL-6511:
----------------------------------
Summary: Bootstrap S3 storage plugin is misleading
Key: DRILL-6511
URL: https://issues.apache.org/jira/browse/DRILL-6511
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.13.0
Reporter: Paul Rogers
When using the above approach, it appears that one must specify the endpoint:
{code}
"connection": "s3a://<bucket-name>/",
"config": {
"fs.s3a.access.key": "<key>",
"fs.s3a.secret.key": "<key>",
"fs.s3a.endpoint": "s3.us-west-1.amazonaws.com"
},
{code}
I could not get the above to work using the pattern in the default S3 config:
{code}
connection: "s3a://my.bucket.location.com",
{code}
Using the endpoint is how all S3a examples I could find described the usage. It is also consistent with the [s3a documentation|https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/index.html#S3A].
Note that the {{my.bucket.location.com}} example is never right. The format must be valid for Amazon.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)