[HDFS-6422] getfattr in CLI doesn't throw exception or return non-0 return code when xattr doesn't exist - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Blocker
Resolution: Fixed
Affects Version/s: 2.5.0, 3.0.0-alpha1
Fix Version/s: 2.5.0
Component/s: None
Labels:
None

Target Version/s:

2.5.0
Hadoop Flags:

Reviewed

Description

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.

Attachments

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

editsStored
22/Jul/14 14:59
5 kB
Charles Lamb
HDFS-6422.005.patch
16/Jul/14 22:36
23 kB
Charles Lamb
HDFS-6422.006.patch
17/Jul/14 19:52
24 kB
Charles Lamb
HDFS-6422.007.patch
21/Jul/14 21:00
28 kB
Charles Lamb
HDFS-6422.008.patch
22/Jul/14 01:45
33 kB
Charles Lamb
HDFS-6422.009.patch
22/Jul/14 14:59
34 kB
Charles Lamb
HDFS-6422.010.patch
22/Jul/14 19:29
36 kB
Charles Lamb
HDFS-6422.1.patch
16/May/14 23:34
5 kB
Charles Lamb
HDFS-6422.2.patch
19/May/14 22:30
26 kB
Charles Lamb
HDFS-6422.3.patch
21/May/14 22:22
32 kB
Charles Lamb
HDFS-6474.4.patch
15/Jul/14 21:13
21 kB
Charles Lamb

Issue Links

is blocked by

HDFS-6464 Support multiple xattr.name parameters for WebHDFS getXAttrs.

Closed

Activity

People

Assignee:: Charles Lamb

Reporter:: Charles Lamb

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 16/May/14 22:22

Updated:: 12/May/16 18:14

Resolved:: 23/Jul/14 19:09