[
https://issues.apache.org/jira/browse/HIVE-16983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888001#comment-16888001
]
Alexandre Pastorino commented on HIVE-16983:
--------------------------------------------
Hello.
I ran into the exact same problem and the cause on my side was that an
"External Account" overrode the role-based authorizations for impala and hue
only.
Which means hive, hdfs, hadoop and spark worked properly but impala was
displaying that error when trying to open a file R or W.
I hope it helps someone in the fututre!
External Account configuration is in the "Administration > External Accounts"
menu
> getFileStatus on accessible s3a://[bucket-name]/folder: throws
> com.amazonaws.services.s3.model.AmazonS3Exception: Forbidden (Service: Amazon
> S3; Status Code: 403; Error Code: 403 Forbidden;
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-16983
> URL: https://issues.apache.org/jira/browse/HIVE-16983
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 2.1.1
> Environment: Hive 2.1.1 on Ubuntu 14.04 AMI in AWS EC2, connecting to
> S3 using s3a:// protocol
> Reporter: Alex Baretto
> Assignee: Vlad Gudikov
> Priority: Major
> Fix For: 2.1.1
>
> Attachments: HIVE-16983-branch-2.1.patch
>
>
> I've followed various published documentation on integrating Apache Hive
> 2.1.1 with AWS S3 using the `s3a://` scheme, configuring `fs.s3a.access.key`
> and
> `fs.s3a.secret.key` for `hadoop/etc/hadoop/core-site.xml` and
> `hive/conf/hive-site.xml`.
> I am at the point where I am able to get `hdfs dfs -ls s3a://[bucket-name]/`
> to work properly (it returns s3 ls of that bucket). So I know my creds,
> bucket access, and overall Hadoop setup is valid.
> hdfs dfs -ls s3a://[bucket-name]/
>
> drwxrwxrwx - hdfs hdfs 0 2017-06-27 22:43
> s3a://[bucket-name]/files
> ...etc.
> hdfs dfs -ls s3a://[bucket-name]/files
>
> drwxrwxrwx - hdfs hdfs 0 2017-06-27 22:43
> s3a://[bucket-name]/files/my-csv.csv
> However, when I attempt to access the same s3 resources from hive, e.g. run
> any `CREATE SCHEMA` or `CREATE EXTERNAL TABLE` statements using `LOCATION
> 's3a://[bucket-name]/files/'`, it fails.
> for example:
> >CREATE EXTERNAL TABLE IF NOT EXISTS mydb.my_table ( my_table_id string,
> >my_tstamp timestamp, my_sig bigint ) ROW FORMAT DELIMITED FIELDS TERMINATED
> >BY ',' LOCATION 's3a://[bucket-name]/files/';
> I keep getting this error:
> >FAILED: Execution Error, return code 1 from
> >org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got exception:
> >java.nio.file.AccessDeniedException s3a://[bucket-name]/files: getFileStatus
> >on s3a://[bucket-name]/files:
> >com.amazonaws.services.s3.model.AmazonS3Exception: Forbidden (Service:
> >Amazon S3; Status Code: 403; Error Code: 403 Forbidden; Request ID:
> >C9CF3F9C50EF08D1), S3 Extended Request ID:
> >T2xZ87REKvhkvzf+hdPTOh7CA7paRpIp6IrMWnDqNFfDWerkZuAIgBpvxilv6USD0RSxM9ymM6I=)
> This makes no sense. I have access to the bucket as one can see in the hdfs
> test. And I've added the proper creds to hive-site.xml.
> Anyone have any idea what's missing from this equation?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
