[ https://issues.apache.org/jira/browse/HDFS-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829521#comment-15829521 ]
Akira Ajisaka commented on HDFS-11084: -------------------------------------- Some comments from me: * Would you rename the new directory from {{/tmp}} to {{/stickybit}} or something to specify that the directory has sticky bit? * Would you add a entry for the directory to {{writtenFiles}} to pass the regression test? I'm thinking HADOOP-13508 should be backported to branch-2 as well? What do you think, [~jojochuang]? > 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 > Assignee: 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org