[HIVE-16913] Support per-session S3 credentials

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: pull-request-available
• Assignee: Vihang Karajgaonkar Assign to me
• Reporter: Vihang Karajgaonkar
• Created: 16/Jun/17 17:29
• Updated: 07/Nov/22 00:22

Description

Currently, the credentials needed to support Hive-on-S3 (or any other cloud-storage) need to be to the hive-site.xml. Either using a hadoop credential provider or by adding the keys in the hive-site.xml in plain text (unsecure)

This limits the usecase to using a single S3 key. If we configure per bucket s3 keys like described here it exposes the access to all the buckets to all the hive users.

It is possible that there are different sets of users who would not like to share there buckets and still be able to process the data using Hive. Enabling session level credentials will help solve such use-cases. For example, currently this doesn't work

set fs.s3a.secret.key=my_secret_key;
set fs.s3a.access.key=my_access.key;

Because metastore is unaware of the the keys. This doesn't work either

set fs.s3a.secret.key=my_secret_key;
set fs.s3a.access.key=my_access.key;
set metaconf:fs.s3a.secret.key=my_secret_key;
set metaconf:fs.s3a.access.key=my_access_key;

This is because only a certain metastore configurations defined in HiveConf.MetaVars are allowed to be set by the user. If we enable the above approaches we could potentially allow multiple S3 credentials on a per-session level basis.

Issue Links

• depends upon: HADOOP-14556 S3A to support Delegation Tokens
• links to: GitHub Pull Request #3542