[
https://issues.apache.org/jira/browse/DRILL-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174695#comment-16174695
]
ASF GitHub Bot commented on DRILL-5438:
---------------------------------------
GitHub user xhochy opened a pull request:
https://github.com/apache/drill/pull/952
DRILL-5438: Amazon S3 bucket can't be queried directly at root
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xhochy/drill DRILL-5438
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/952.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #952
----
commit 8e43de6970a74fa001eabfa20f88da97feedad5b
Author: Korn, Uwe <[email protected]>
Date: 2017-09-21T12:52:58Z
DRILL-5438: Amazon S3 bucket can't be queried directly at root
----
> Amazon S3 bucket can't be queried directly at root
> --------------------------------------------------
>
> Key: DRILL-5438
> URL: https://issues.apache.org/jira/browse/DRILL-5438
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.10.0
> Reporter: Alon P
> Labels: S3Plugin
>
> It is not possible to query the root directory of Amazon S3 bucket.
> For example, the contents of the bucket are:
> /a/file1.json
> /b/file2.json
> /c/file3.json
> and I'd like to do something like that: select * from s3.`root`;
> and that it'll return the contents of file1.json+file2.json+file3.json
> I couldn't find how to make it work.
> ---
> This is a major issue as I believe many Amazon S3 users put files directly
> into the root of the bucket or use a hash prefix as suggested by Amazon for a
> good performance in a high request rate configuration
> (http://docs.aws.amazon.com/AmazonS3/latest/dev/request-rate-perf-considerations.html).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
