Hi Alex, Check out the "Setting up Apache Drill for use with S3" section of this article I wrote: http://www.dremio.com/blog/using-sql-to-interface-with-google-analytics-data-stored-on-amazon-s3/
It should handle what you're trying to do. In particular, make sure your storage plugin for s3 is set up as indicated, since I didn't see you mention its configuration in your email. Best of luck! Nathan On Mon, Nov 16, 2015 at 3:21 PM, Mikhailau, Alex <[email protected]> wrote: > Guys, > > I keep getting the following exception: > > org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR: > IllegalArgumentException: AWS Access Key ID and Secret Access Key must be > specified as the username or password (respectively) of a s3 URL, or by > setting the fs.s3.awsAccessKeyId or fs.s3.awsSecretAccessKey properties > (respectively). [Error Id: 919f3351-6b9a-4f8b-ac9d-cea5b6a8be1f on > ip-172-31-59-234.ec2.internal:31010] > > > 1. I followed the set up at > https://www.mapr.com/blog/bootstrap-apache-drill-amazon-emr. > > > 2. I set up /opt/mapr/drill/drill-1.2.0/conf/core-site.xml > > <configuration> > > > <property><name>fs.s3.impl</name><value>org.apache.hadoop.fs.s3native.NativeS3FileSystem</value></property> > > <property><name>fs.s3n.impl</name><value>org.apache.hadoop.fs.s3native.NativeS3FileSystem</value></property> > > <property><name>fs.s3.block.size</name><value>67108864</value></property> > <property><name>fs.s3n.block.size</name><value>67108864</value></property> > <property><name>fs.s3.awsAccessKeyId</name><value>XXXXXX</value></property> > <property><name>fs.s3.awsSecretAccessKey</name><value>YYYYYY</value></property> > <property><name>fs.s3n.awsAccessKeyId</name><value>XXXXXX</value></property> > <property><name>fs.s3n.awsSecretAccessKey</name><value>YYYYYY</value></property> > > <property> > <name>hbase.table.namespace.mappings</name> > <value>*:/user/${user.name}</value> > </property> > > </configuration> > > 3. I’ve re-started drill > /opt/mapr/bin/maprcli node services -name > drill-bits -action restart -nodes ip-172-31-57-10.ec2.internal > > 4. Running a query like this - SELECT hostname FROM sys.drillbits WHERE > `current` = true; - or any other yields the same exception. > > 5. Running hadoop fs -ls s3://bucket/ lists files just fine. > > Can anyone please help figure out what the problem is with Drill not able to > access S3 or run any queries for that matter from the sys table? > > Greatly appreciated. > > Thank you, > > Alex > ********************************************************** > > MLB.com: Where Baseball is Always On
