[
https://issues.apache.org/jira/browse/HDFS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837651#action_12837651
]
Milind Bhandarkar commented on HDFS-240:
----------------------------------------
Interesting. Wonder how this relates to HDFS-13.
Especially Doug's comment at
https://issues.apache.org/jira/browse/HDFS-13?focusedCommentId=12558701&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12558701
which says "But we shouldn't let it limit what names are possible in various
filesystems as we do today: we should support their full range, using escapes
where necessary."
This must be fixed before we can even think of "backward compatibility".
> Should HDFS restrict the names used for files?
> ----------------------------------------------
>
> Key: HDFS-240
> URL: https://issues.apache.org/jira/browse/HDFS-240
> Project: Hadoop HDFS
> Issue Type: New Feature
> 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.
