[
https://issues.apache.org/jira/browse/SQOOP-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704807#comment-16704807
]
Steve Loughran commented on SQOOP-3410:
---------------------------------------
FWIW, that option was put in to let people provide per-bucket login secrets
in practise it hasn't worked well because hive & other tools make the
credential provider config option final: you can't update it.
For later Hadoop versions, we've modified password lookup so that the s3a
connectors explicitly scan the existing keystores for the keys
"fs.s3a.bucket.$BUCKET.secret.key", "fs.s3a.bucket.$BUCKET.access.key" and
"fs.s3a.bucket.$BUCKET.session.key" so that you can have bucket-specific login
options in the same file as others.
> Test S3 import with fs.s3a.security.credential.provider.path
> ------------------------------------------------------------
>
> Key: SQOOP-3410
> URL: https://issues.apache.org/jira/browse/SQOOP-3410
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Boglarka Egyed
> Assignee: Boglarka Egyed
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: SQOOP-3410.patch
>
>
> Based on
> [https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/index.html#Configure_the_hadoop.security.credential.provider.path_property]
> property fs.s3a.security.credential.provider.path can also be used for
> passing the location of the credential store. This should be also tested and
> documented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
