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 "Wei-Chiu Chuang (JIRA)" <ji...@apache.org> on 2017/02/10 23:42:41 UTC
[jira] [Updated] (HDFS-11084) OIV ReverseXML processor does not
recognize sticky bit
[ https://issues.apache.org/jira/browse/HDFS-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei-Chiu Chuang updated HDFS-11084:
-----------------------------------
Attachment: HDFS-11804.branch-2.002.patch
Thanks [~ajisakaa].
Good idea use a directory name other than /tmp. In practice /tmp is often associated with sticky bit though.
Attached a second patch.
I think the patch can go into trunk as well. HADOOP-13508 can go into branch-2.8 for release in 2.8.1.
> 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.002.patch, 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org