[
https://issues.apache.org/jira/browse/HADOOP-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760547#action_12760547
]
Steve Loughran commented on HADOOP-6287:
----------------------------------------
This is getting very complex, and I am starting to thing -1 is the correct
reaction to this problem. There is a risk that this ends up a bit like the XSD
type system.
I'm also worried about the impact this has on my plans to add support for >1
configuration back end, including LDAP.
FWIW, in the SmartFrog syntax we have basic math symbols, stops the caller
having to care about stuff. But it does mean the type system needs to
differentiate between string and numeric values,
{code}
dfs.balance.bandwidthPerSec (1024 * 1024);
dfs.block.size (65536 * 1024);
dfs.blockreport.intervalMsec (60 * 60 * 1000);
mapred.tasktracker.expiry.interval (10 * 60 * 1000);
mapred.jobtracker.retirejob.check (60 * 1000);
{code}
Of course, then you need functions, evaluation order rules, etc, etc, which are
bonus complexity, especially if you start worrying about where that work takes
place, in the getInt/getLong() operation, or everywhere
> Support units for configuration knobs
> -------------------------------------
>
> Key: HADOOP-6287
> URL: https://issues.apache.org/jira/browse/HADOOP-6287
> Project: Hadoop Common
> Issue Type: Improvement
> Components: conf
> Reporter: Arun C Murthy
> Assignee: Eli Collins
> Attachments: hadoop-6287-1.patch
>
>
> We should add support for units in our Configuration system so that we can
> specify values to be *1GB* or *1MB* rather than forcing every component which
> consumes such values to be aware of these.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
