[
https://issues.apache.org/jira/browse/HDFS-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166981#comment-15166981
]
Chris Douglas commented on HDFS-9847:
-------------------------------------
bq. Adding week and year in hadoop-common is wanting to support to more
differnet units in subclassing(HBase, Hive , etc)rather just HDFS.
Is {{21d}} not sufficiently clear? What {{TimeUnit}} provides seems sufficient.
bq. There are some places using timeSecondInterval variable in int type, so I
define getIntTimeSeconds in Configuration. It nedd not cast type from long to
int each time.
Adding new methods to parameterize {{getTimeDuration}} is unnecessary. The
caller should cast the result if it's losing precision.
> 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, HDFS-9847.002.patch,
> timeduration-w-y.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)
