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 "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/11/06 06:03:00 UTC
[jira] [Commented] (HDFS-13941) make storageId in
BlockPoolTokenSecretManager.checkAccess optional
[ https://issues.apache.org/jira/browse/HDFS-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676205#comment-16676205 ]
Sunil Govindan commented on HDFS-13941:
---------------------------------------
Updating Fixed Version to 3.2.1 as this is fixed was not landed on branch-3.2.0 which was closed for RC prep.
> 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
> Fix For: 3.0.4, 3.1.2, 3.3.0, 3.2.1
>
> Attachments: HDFS-13941.00.patch, HDFS-13941.01.patch, HDFS-13941.02.patch, HDFS-13941.branch-3.0.001.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 interface, 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org