hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nigel Daley <nda...@yahoo-inc.com>
Subject Re: [jira] Commented: (HADOOP-667) Path configuration properties should not be comma separated
Date Thu, 02 Nov 2006 16:22:08 GMT
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
>
>


Mime
View raw message