[
https://issues.apache.org/jira/browse/HADOOP-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566841#action_12566841
]
Tsz Wo (Nicholas), SZE commented on HADOOP-2461:
------------------------------------------------
> I think it will confuse users a lot if 010 == 8.
I agree that it might be a problem and such problem is hard to be detected.
How about we make a special syntax for octal? Maybe something like: octal10 = 8
> Configuration should trim property names and accept decimal, hexadecimal, and
> octal numbers
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-2461
> URL: https://issues.apache.org/jira/browse/HADOOP-2461
> Project: Hadoop Core
> Issue Type: Improvement
> Components: conf
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Minor
> Attachments: 2461_20071218.patch
>
>
> I suggest two improvements in reading configuration:
> - Suppose we have the following property in a conf file.
> {code}
> <property>
> <name>
> testing.property</name>
> <value>something</value>
> </property>
> {code}
> Try to get it by
> {code}
> Configuration conf = new Configuration();
> String value = conf.get("testing.property"); //value == null here
> {code}
> We will get null since there is an eol in
> {code}
> <name>
> testing.property</name>
> {code}
> I suggest to trim all property names.
> - I also suggest configuration to accept decimal, hexadecimal, and octal
> numbers (e.g. 011 is 9, 0xA is 10)
> It can be easily done by replacing Integer.parseInt(...) with
> Integer.decode(...) in Configuration.getInt(...), similarly, in
> Configuration.getLong(...).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
