[ 
https://issues.apache.org/jira/browse/HADOOP-15319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404781#comment-16404781
 ] 

Rushabh S Shah edited comment on HADOOP-15319 at 3/19/18 1:10 PM:
------------------------------------------------------------------

[~saurabhpadhy]: Can you create some sample files and directories and post the 
result of {{hadoop fs -ls}} before and after the rm command.
 Also post the {{out stream}} after you run the {{rm}} command.

I am not able to reproduce the error that you are seeing.
That way I will replicate the same directory structure on my side and will run 
the exact same commands that you will run.
Please don't forget to quote the path on {{ls}} and {{rm}} commands.
  


was (Author: shahrs87):
[~saurabhpadhy]: Can you create some sample files and directories and post the 
result of {{hadoop fs -ls}} before and after the rm command.
Also post the {{out stream}} after you run the {{rm}} command.

I am not able to reproduce the error that you are seeing.
 

> hadoop fs -rm command misbehaves on recent hadoop version 2.5.0
> ---------------------------------------------------------------
>
>                 Key: HADOOP-15319
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15319
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: bin
>    Affects Versions: 2.8.2
>            Reporter: Saurabh Padhy
>            Priority: Major
>
> This issue is regarding hadoop fs -rm command. 
> In hadoop version 2.4.0 when we execute "hadoop fs -rm /a/b/c/*",
> It removes the files inside the c directory only.
> But in case of versions higher to 2.8.2,
> When we execute "hadoop fs -rm /a/b/c/**" or "hdfs dfs -rm /a/b/c/**"
> It removes the inside files and directory as well.
> Please look into the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to