hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14251) Credential provider should handle property key deprecation
Date Wed, 16 Aug 2017 12:47:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128737#comment-16128737

Steve Loughran commented on HADOOP-14251:

Not quite yet.

# # Looking @ deprecation in a detail I've never done before, I can see that you can actually
set a custom deprecation message, built with {{.DeprecatedKeyInfo.getWarningMessage()}}. I
think we should somehow include that in the generated message, even if we still say it came
from a credential provider (maybe also: list its Path?)
# Also need to use the{{getAndSetAccessed}} as a guard to printing the warning, so as to stop
it reappearing on future reads.

> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message