[HADOOP-8139] Path does not allow metachars to be escaped

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.23.3, 3.0.0-alpha1
• Component/s: fs
• Assignee: Unassigned
• Reporter: Daryn Sharp
• Created: 05/Mar/12 17:26
• Updated: 12/May/16 18:24

Description

Path converts "\" into "/", probably for windows support? This means it's impossible for the user to escape metachars in a path name. Glob expansion can have deadly results.

Here are the most egregious examples. A user accidentally creates a path like "/user/me/*/file". Now they want to remove it.

"hadoop fs -rmr -skipTrash '/user/me/\*'" becomes...
"hadoop fs -rmr -skipTrash /user/me/*"

• User/Admin: Nuked their home directory or any given directory

"hadoop fs -rmr -skipTrash '\*'" becomes...
"hadoop fs -rmr -skipTrash /*"

• User: Deleted everything they have access to on the cluster
• Admin: Nukes the entire cluster

Note: FsShell is shown for illustrative purposes, however the problem is in the Path object, not FsShell.

Issue Links

• relates to: HADOOP-8079 Proposal for enhancements to Hadoop for Windows Server and Windows Azure development and runtime environments

Sub-Tasks

• Handle paths using back slash as path separator for windows only: Closed
• FsShell needs to handle quoted metachars: Resolved