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

Uwe L. Korn commented on DRILL-4959:
------------------------------------

Note that the linked blog article is outdated. For connecting to S3, there 
should be no requirement anymore for jets3t if you use the s3a backend.

Ensure that you have used the configuration as described on 
https://drill.apache.org/docs/s3-storage-plugin/ and also used {{s3a://}} in 
your URL. {{s3://}} and {{s3n://}} are still available but outdated. 

> Drill 8.1 not able to connect to S3
> -----------------------------------
>
>                 Key: DRILL-4959
>                 URL: https://issues.apache.org/jira/browse/DRILL-4959
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>            Reporter: Gopal Nagar
>
> Hi Team,
> I have followed below details to integrate Drill with AWS S3. Query keep 
> running for hours and doesn't display any output (I am querying only 2 row 
> file from S3).
> Reference link
> -------------------
> https://abhishek-tiwari.com/post/reflections-on-apache-drill
> https://drill.apache.org/docs/s3-storage-plugin/ 
> Query Format (Tried from UI & CLI)
> ----------------------------------------------------
> select * from `s3`.`hive.csv` LIMIT 10;
> select * from `s3`.`bucket_name/hive.csv` LIMIT 10;
> After seeing below log, I tried including jets3t-0.9.3.jar in jars directory 
> but it doesn't fix my problem.
> Log Details
> --------------
> 2016-10-24 17:00:02,461 [27f1c1ec-d82e-ba2a-2840-e7104320418f:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 27f1c1ec-d82e-ba2a-2840-e7104320418f: select * from `s3`.`hive.csv` LIMIT 10
> 2016-10-24 17:00:02,479 [drill-executor-39] ERROR 
> o.a.d.exec.server.BootStrapContext - 
> org.apache.drill.exec.work.foreman.Foreman.run() leaked an exception.
> java.lang.NoClassDefFoundError: org/jets3t/service/S3ServiceException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to