You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ajay Kumar (JIRA)" <ji...@apache.org> on 2018/09/25 18:48:00 UTC
[jira] [Updated] (HDFS-13941) make storageId in
BlockPoolTokenSecretManager.checkAccess optional
[ https://issues.apache.org/jira/browse/HDFS-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ajay Kumar updated HDFS-13941:
------------------------------
Description: change in BlockPoolTokenSecretManager.checkAccess by [#HDDS-9807] breaks backward compatibility for Hadoop 2 clients. Since SecretManager is marked for public audience we should add a overloaded function to allow Hadoop 2 clients to work with it. (was: change in BlockPoolTokenSecretManager.checkAccess by [HDDS-9807] breaks backward compatibility for Hadoop 2 clients. Since SecretManager is marked for public audience we should add a overloaded function to allow Hadoop 2 clients to work with it.)
> make storageId in BlockPoolTokenSecretManager.checkAccess optional
> ------------------------------------------------------------------
>
> Key: HDFS-13941
> URL: https://issues.apache.org/jira/browse/HDFS-13941
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Ajay Kumar
> Priority: Major
>
> change in BlockPoolTokenSecretManager.checkAccess by [#HDDS-9807] breaks backward compatibility for Hadoop 2 clients. Since SecretManager is marked for public audience we should add a overloaded function to allow Hadoop 2 clients to work with it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org