drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5438) Amazon S3 bucket can't be queried directly at root
Date Sun, 24 Sep 2017 01:36:01 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178038#comment-16178038
] 

ASF GitHub Bot commented on DRILL-5438:
---------------------------------------

Github user paul-rogers commented on the issue:

    https://github.com/apache/drill/pull/952
  
    Unit tests for S3 are difficult as we can't guarantee that each developer who runs the
tests has visibility. @ilooner is adding test categories. Perhaps we can use one of those
to create S3 tests that require some specific S3 setup, perhaps in a user-specific Maven properties
file. Thoughts?


> 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)

Mime
View raw message