You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/05/05 18:33:12 UTC
[jira] [Updated] (HDFS-240) Should HDFS restrict the names used for
files?
[ https://issues.apache.org/jira/browse/HDFS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HDFS-240:
-----------------------------
Affects Version/s: 2.7.2
Target Version/s: 3.0.0
Hadoop Flags: Incompatible change
This would be great to get into the next major release, setting the target version for tracking.
We have "-renameReserved" functionality introduced in HDFS-5709 that we can leverage to rename invalid paths on upgrade.
> 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
> Affects Versions: 2.7.2
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org