[ http://issues.apache.org/jira/browse/HADOOP-667?page=comments#action_12447522 ] Doug Cutting commented on HADOOP-667: -------------------------------------
For the record, we used to permit comma- or space- delimited lists. Spaces were removed for better operation under Windows, where spaces are common in directory names. We could fix this by quoting, or with nested xml tags. But I would give this a very low priority. (Has anyone actually complained because they need to specify a path with a comma? Do we expect anyone will anytime soon? If they did, would the workaround be difficult or non-obvious?) > Path configuration properties should not be comma separated > ----------------------------------------------------------- > > Key: HADOOP-667 > URL: http://issues.apache.org/jira/browse/HADOOP-667 > Project: Hadoop > Issue Type: Bug > Components: fs > Affects Versions: 0.7.2 > Reporter: Nigel Daley > Priority: Minor > > A few configuration properties allow multiple directory paths separated by > comma's (,). Since comma is a valid character for a directory name, it > should not be used as a path separator. > At a minimum, this applies to these properties: > mapred.local.dir > dfs.name.dir > [ I also wonder how robust the implementation is against paths that contain > spaces. ] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
