Configuring Hive access for S3A
You must configure specific properties for client applications such as Hive to access the Ozone data store using S3A.
- You must import the CA certificate to run Ozone S3 Gateway from the S3A filesystem.
- You must configure the following Hive properties using the
Cluster-wide Advanced Configuration Snippet (Safety Valve) for
core-site.xml:
fs.s3a.bucket.<<bucketname>>.access.key = <accesskey> fs.s3a.bucket.<<bucketname>>.secret.key = <secret> fs.s3a.endpoint = <Ozone S3 endpoint url> fs.s3a.bucket.probe = 0 fs.s3a.change.detection.version.required = false fs.s3a.path.style.access = true fs.s3a.change.detection.mode = none
- You must provide the required permissions in Ranger to the user running the
queries. Consider the following example of providing a user with
all
permissions. You can change the permissions based on your requirements.- Assign the user with
all
permissions to theDatabase
,table/udf
, andURL
resources in a HadoopSQL resource-based policy. - Assign the user with
S3_VOLUME_POLICY
in an Ozone policy.
- Assign the user with