[
https://issues.apache.org/jira/browse/HADOOP-17704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346070#comment-17346070
]
Wei-Chiu Chuang commented on HADOOP-17704:
------------------------------------------
package org.apache.hadoop.fs.azurebfs.extensions
[−] SASTokenProvider 12
|| ||Change||Effect||
||1|Field *APPEND_OPERATION* has been renamed to
*SET_PROPERTIES_OPERATION*.|Recompilation of a client program may be terminated
with the message: cannot find variable *APPEND_OPERATION* in
*SASTokenProvider*.|
||2|Field *CONCAT_SOURCE_OPERATION* has been renamed to
*CHECK_ACCESS_OPERATION*.|Recompilation of a client program may be terminated
with the message: cannot find variable *CONCAT_SOURCE_OPERATION* in
*SASTokenProvider*.|
||3|Field *CONCAT_TARGET_OPERATION* has been renamed to
*CREATE_DIRECTORY_OPERATION*.|Recompilation of a client program may be
terminated with the message: cannot find variable *CONCAT_TARGET_OPERATION* in
*SASTokenProvider*.|
||4|Field *CREATEFILE_OPERATION* has been renamed to
*CREATE_FILE_OPERATION*.|Recompilation of a client program may be terminated
with the message: cannot find variable *CREATEFILE_OPERATION* in
*SASTokenProvider*.|
||5|Field *EXECUTE_OPERATION* has been renamed to
*DELETE_RECURSIVE_OPERATION*.|Recompilation of a client program may be
terminated with the message: cannot find variable *EXECUTE_OPERATION* in
*SASTokenProvider*.|
||6|Field *GETACL_OPERATION* has been renamed to
*GET_ACL_OPERATION*.|Recompilation of a client program may be terminated with
the message: cannot find variable *GETACL_OPERATION* in *SASTokenProvider*.|
||7|Field *GETFILESTATUS_OPERATION* has been renamed to
*GET_STATUS_OPERATION*.|Recompilation of a client program may be terminated
with the message: cannot find variable *GETFILESTATUS_OPERATION* in
*SASTokenProvider*.|
||8|Field *LISTSTATUS_OPERATION* has been renamed to
*GET_PROPERTIES_OPERATION*.|Recompilation of a client program may be terminated
with the message: cannot find variable *LISTSTATUS_OPERATION* in
*SASTokenProvider*.|
||9|Field *MKDIR_OPERATION* has been renamed to *LIST_OPERATION*.|Recompilation
of a client program may be terminated with the message: cannot find variable
*MKDIR_OPERATION* in *SASTokenProvider*.|
||10|Field *SETACL_OPERATION* has been renamed to
*SET_ACL_OPERATION*.|Recompilation of a client program may be terminated with
the message: cannot find variable *SETACL_OPERATION* in *SASTokenProvider*.|
||11|Field *SETOWNER_OPERATION* has been renamed to
*SET_OWNER_OPERATION*.|Recompilation of a client program may be terminated with
the message: cannot find variable *SETOWNER_OPERATION* in *SASTokenProvider*.|
||12|Field *SETPERMISSION_OPERATION* has been renamed to
*SET_PERMISSION_OPERATION*.|Recompilation of a client program may be terminated
with the message: cannot find variable *SETPERMISSION_OPERATION* in
*SASTokenProvider*.|
> HADOOP-16916 changed interface SASTokenProvider fields, breaking
> compatibility between 3.3.0 and 3.3.1
> -------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-17704
> URL: https://issues.apache.org/jira/browse/HADOOP-17704
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Affects Versions: 3.3.1
> Reporter: Wei-Chiu Chuang
> Priority: Blocker
>
> I understand HADOOP-16730/HADOOP-16916 is specifically made for Ranger, but I
> am not sure how Ranger consumes this feature. The interface SASTokenProvider
> has a number of member fields that changed variable names in HADOOP-16916,
> breaking the compatibility between 3.3.0 and 3.3.1.
> As a matter of fact, the feature HADOOP-16730 itself was merged in 3.3.0 not
> 3.3.1. I just corrected it today.
> Raise this jira and mark it as a blocker for 3.3.1. But if this isn't a big
> deal then we can downgrade, because, well, this feature was not officially in
> the 3.3.0 release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
