[
https://issues.apache.org/jira/browse/HDFS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HDFS-240:
----------------------------------
Description:
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?
was:
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?
> 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 was sent by Atlassian JIRA
(v6.2#6252)
