[
https://issues.apache.org/jira/browse/HDFS-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-13941:
---------------------------------
Description:
Change in {{BlockPoolTokenSecretManager.checkAccess}} by
[HDDS-9807|https://issues.apache.org/jira/browse/HDFS-9807] breaks backward
compatibility for applications using the private API (we've run into such apps).
Although there is no compatibility guarantee for the private interests, we can
restore the original version of checkAccess as an overload.
was: change in {{BlockPoolTokenSecretManager.checkAccess}} by
[HDDS-9807|https://issues.apache.org/jira/browse/HDFS-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
> Assignee: Ajay Kumar
> Priority: Major
> Attachments: HDFS-13941.00.patch, HDFS-13941.01.patch,
> HDFS-13941.02.patch
>
>
> Change in {{BlockPoolTokenSecretManager.checkAccess}} by
> [HDDS-9807|https://issues.apache.org/jira/browse/HDFS-9807] breaks backward
> compatibility for applications using the private API (we've run into such
> apps).
> Although there is no compatibility guarantee for the private interests, we
> can restore the original version of checkAccess as an overload.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]