[
https://issues.apache.org/jira/browse/HADOOP-14251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131963#comment-16131963
]
Steve Loughran commented on HADOOP-14251:
-----------------------------------------
I think the credential code could just hand off to the Configuration one; its
telling the user off once and only once per process...the origin is moot. All
that's needed for the credential API is to list the origin of the key for
future diags. Actually, the standard one could maybe do that too, given that
provenance is tracked
> Credential provider should handle property key deprecation
> ----------------------------------------------------------
>
> Key: HADOOP-14251
> URL: https://issues.apache.org/jira/browse/HADOOP-14251
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.6.0
> Reporter: John Zhuge
> Assignee: John Zhuge
> Priority: Critical
> Attachments: HADOOP-14251.001.patch, HADOOP-14251.002.patch,
> HADOOP-14251.003.patch
>
>
> The properties with old keys stored in a credential store can not be read via
> the new property keys, even though the old keys have been deprecated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
