[ https://issues.apache.org/jira/browse/HDFS-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HDFS-6422: ------------------------------ Priority: Blocker (was: Major) I looked into this more with [~clamb] and there's a compatibility concern with some code in WebHDFS / XAttrNameParam: {code} private static Domain DOMAIN = new Domain(NAME, Pattern.compile("^(user\\.|trusted\\.|system\\.|security\\.).+")); {code} Doing client-side validation of the namespace means we can't later add new namespaces and have them also be accessible by an old client. Since we already do server-side validation, I think we can just remove this check. Let's fix this before we release 2.5.0. Raising priority to a blocker since it's a compat concern and should be easy to fix. > getfattr in CLI doesn't throw exception or return non-0 return code when > xattr doesn't exist > -------------------------------------------------------------------------------------------- > > Key: HDFS-6422 > URL: https://issues.apache.org/jira/browse/HDFS-6422 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 3.0.0, 2.5.0 > Reporter: Charles Lamb > Assignee: Charles Lamb > Priority: Blocker > Attachments: HDFS-6422.1.patch, HDFS-6422.2.patch, HDFS-6422.3.patch, > HDFS-6474.4.patch > > > If you do > hdfs dfs -getfattr -n user.blah /foo > and user.blah doesn't exist, the command prints > # file: /foo > and a 0 return code. > It should print an exception and return a non-0 return code instead. -- This message was sent by Atlassian JIRA (v6.2#6252)