[
https://issues.apache.org/jira/browse/HADOOP-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720390#action_12720390
]
Robert Chansler commented on HADOOP-6059:
-----------------------------------------
Of course, the more restricted the name space, the easier the QA function. And
you never have to explain how globbing works with Farsi. The HDFS milieu is
complicated by the deliberate conflation of file names and URIs. Maybe there
are three broad options:
1. Any string can be a name, except no '/', NUL, or "", "." or "..".
2. Any 8-bit character string can be a name, except no '/', NUL, or "", "." or
"..". (loosely, like POSIX)
3. Any non-empty string from a specified list of printing characters.
([A-Z,a-z,0-9,_,-,:], for example)
> Should HDFS restrict the names used for files?
> ----------------------------------------------
>
> Key: HADOOP-6059
> URL: https://issues.apache.org/jira/browse/HADOOP-6059
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Robert Chansler
>
> When reviewing the consequences of Hadoop:6017 (the name system could not
> start because a file name interpreted as a regex caused a fault), the
> discussion turned to improving the test set for file system functions by
> broadening the set of names used for testing. Presently, HDFS allows any name
> without a slash. _Should the space of names be restricted?_ If most funny
> names are unintended, maybe the user would benefit from an early error
> indication. A contrary view is that restricting names is so 20th-century.
> Should be or shouldn't we?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
