[
https://issues.apache.org/jira/browse/HDFS-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159852#comment-15159852
]
Arpit Agarwal edited comment on HDFS-9847 at 2/23/16 11:29 PM:
---------------------------------------------------------------
Yes {{Configuration::getTimeDuration}} looks like it does exactly what we want.
You may wish to augment it with the additional time units suggested by Steve
for completeness. Also support 'w' for weeks, at least one of our config
settings defaults to weeks (dfs.datanode.scan.period.hours).
was (Author: arpitagarwal):
Yes {{Configuration::getTimeDuration}} looks like it does exactly what we want.
You may wish to augment it with the additional time units suggested by Steve
for completeness.
> HDFS configuration without time unit name should accept friendly time units
> ---------------------------------------------------------------------------
>
> Key: HDFS-9847
> URL: https://issues.apache.org/jira/browse/HDFS-9847
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: 2.7.1
> Reporter: Lin Yiqun
> Assignee: Lin Yiqun
> Attachments: HDFS-9847.001.patch
>
>
> In HDFS-9821, it talks about the issue of leting existing keys use friendly
> units e.g. 60s, 5m, 1d, 6w etc. But there are som configuration key names
> contain time unit name, like {{dfs.blockreport.intervalMsec}}, so we can make
> some other configurations which without time unit name to accept friendly
> time units. The time unit {{seconds}} is frequently used in hdfs. We can
> updating this configurations first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
