sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3410) Test S3 import with fs.s3a.security.credential.provider.path
Date Mon, 03 Dec 2018 11:33:01 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707042#comment-16707042
] 

Steve Loughran commented on SQOOP-3410:
---------------------------------------

# HADOOP-14507
# {{ fs.s3a.security.credential.provider.path}} has not been pulled/deprecated at all, not
yet. Still does something nice which lets you point @ a different  JCEKS file with the keys
going by the classic (unbucketed) names. Not sure if I'd want to cut it for that reason ...
it just hits a wall with shared keystores and locked down apps

> 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)

Mime
View raw message