[
https://issues.apache.org/jira/browse/HDFS-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745930#comment-15745930
]
Chris Douglas commented on HDFS-11084:
--------------------------------------
Ah, got it. I thought HADOOP-13508 had caused a regression.
AFAIK there's no behavior that depends on {{FsPermission}} ignoring the sticky
bit. The semantics in branch-2 are incorrect, HADOOP-13508 isn't marked as
incompatible... backporting seems OK to me.
> OIV ReverseXML processor does not recognize sticky bit
> ------------------------------------------------------
>
> Key: HDFS-11084
> URL: https://issues.apache.org/jira/browse/HDFS-11084
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
> Affects Versions: 2.8.0
> Reporter: Wei-Chiu Chuang
> Attachments: HDFS-11804.branch-2.patch
>
>
> HDFS-10505 added a new feature OIV ReverseXML processor to generate a fsimage
> from a xml file. However, if the files/directories in it has sticky bit,
> ReverseXML processor can not recognize it due to HADOOP-13508.
> It seems HADOOP-13508 is an incompatible change in Hadoop 3. Would it be
> reasonable to add an overloaded FsPermission constructor that uses RawParser
> so that it reads sticky bits correctly? Or is it reasonable to backport
> HADOOP-13508 to branch-2?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
