[
https://issues.apache.org/jira/browse/HADOOP-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689215#comment-13689215
]
Hudson commented on HADOOP-8608:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1436 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1436/])
Move HADOOP-8608 to branch-2.1 (Revision 1494824)
Result = FAILURE
cdouglas :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1494824
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> Add Configuration API for parsing time durations
> ------------------------------------------------
>
> Key: HADOOP-8608
> URL: https://issues.apache.org/jira/browse/HADOOP-8608
> Project: Hadoop Common
> Issue Type: Improvement
> Components: conf
> Affects Versions: 2.1.0-beta
> Reporter: Todd Lipcon
> Assignee: Chris Douglas
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: 8608-0.patch, 8608-1.patch, 8608-2.patch
>
>
> Hadoop has a lot of configurations which specify durations or intervals of
> time. Unfortunately these different configurations have little consistency in
> units - eg some are in milliseconds, some in seconds, and some in minutes.
> This makes it difficult for users to configure, since they have to always
> refer back to docs to remember the unit for each property.
> The proposed solution is to add an API like {{Configuration.getTimeDuration}}
> which allows the user to specify the units with a postfix. For example,
> "10ms", "10s", "10m", "10h", or even "10d". For backwards-compatibility, if
> the user does not specify a unit, the API can specify the default unit, and
> warn the user that they should specify an explicit unit instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
