You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/08/17 19:49:20 UTC
[jira] [Commented] (HADOOP-13505) Fuzzy match issue in Hadoop
commands
[ https://issues.apache.org/jira/browse/HADOOP-13505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425228#comment-15425228 ]
Steve Loughran commented on HADOOP-13505:
-----------------------------------------
(I should add that this happens to me all the time too. Don't feel bad you got caught out)
> Fuzzy match issue in Hadoop commands
> ------------------------------------
>
> Key: HADOOP-13505
> URL: https://issues.apache.org/jira/browse/HADOOP-13505
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.7.2
> Reporter: Yuanbo Liu
>
> When I used fuzzy match path in hadoop commands, for example
> {noformat}
> hadoop fs -ls /*
> {noformat}
> It printed something like "ls: `/0config': No such file or directory"
> Seems that the fuzzy match will get local path and use local path to list HDFS path.
> Also I tried this
> {noformat}
> hadoop fs -ls "/*"
> {noformat}
> It printed
> {noformat}
> drwxrwx--- - ambari-qa hadoop 0 2016-08-16 00:18 /app-logs/ambari-qa
> {noformat}
> This time the command worked fine, but why did it print the child path of "/*"? This was what I expected:
> {noformat}
> drwxrwx--- - ambari-qa hadoop 0 2016-08-16 00:18 /app-logs
> {noformat}
> this issue widely exists in all kinds of commands that need path parameter.
> So I think the behavior of hadoop commands is confusing, and it need to be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org