You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2006/11/01 18:58:16 UTC
[jira] Created: (HADOOP-667) Path configuration properties should
not be comma separated
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
[jira] Commented: (HADOOP-667) Path configuration properties should
not be comma separated
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-667?page=comments#action_12457978 ]
Owen O'Malley commented on HADOOP-667:
--------------------------------------
I vote that we close this as wont-fix.
> 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
Re: [jira] Commented: (HADOOP-667) Path configuration properties should not be comma separated
Posted by Nigel Daley <nd...@yahoo-inc.com>.
The config files are XML. Seems like multiple name/value pairs
should work.
On Nov 1, 2006, at 11:14 PM, eric baldeschwieler (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/HADOOP-667?
> page=comments#action_12446468 ]
>
> eric baldeschwieler commented on HADOOP-667:
> --------------------------------------------
>
> humm, so how do we specify a list of paths?
>
> sounds like a conversation about quoting conventions is needed
>
>> 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
>
>
[jira] Commented: (HADOOP-667) Path configuration properties should
not be comma separated
Posted by "eric baldeschwieler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-667?page=comments#action_12446468 ]
eric baldeschwieler commented on HADOOP-667:
--------------------------------------------
humm, so how do we specify a list of paths?
sounds like a conversation about quoting conventions is needed
> 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
[jira] Commented: (HADOOP-667) Path configuration properties should
not be comma separated
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (HADOOP-667) Path configuration properties should
not be comma separated
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-667?page=all ]
Owen O'Malley resolved HADOOP-667.
----------------------------------
Resolution: Won't Fix
> 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
[jira] Commented: (HADOOP-667) Path configuration properties should
not be comma separated
Posted by "Yoram Arnon (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-667?page=comments#action_12446390 ]
Yoram Arnon commented on HADOOP-667:
------------------------------------
dfs.data.dir too.
care is required when making a change to maintain backwards compatibility with current configuratins
> 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
[jira] Commented: (HADOOP-667) Path configuration properties should
not be comma separated
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-667?page=comments#action_12457980 ]
Doug Cutting commented on HADOOP-667:
-------------------------------------
> I vote that we close this as wont-fix.
+1
> 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