[
https://issues.apache.org/jira/browse/HDFS-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159140#comment-15159140
]
Steve Loughran commented on HDFS-9847:
--------------------------------------
I agree with the value of this
# this is broader than just HDFS; it is changing Hadoop common and will be
relevant for hadoop core, YARN, anything else subclassing configuration (Hive,
HBase)
# so we'd better support the range of units those apps may need, rather than
just those of HDFS's current needs.
Spark supports time in its configuration; here are some examples
{pre}
25ms (milliseconds)
5s (seconds)
10m or 10min (minutes)
3h (hours)
5d (days)
1y (years)
{code}
I'd like to see the consistent support for the same units —and the ability to
ask for time ranges as millis, rather than just seconds. Sometimes you do want
minimum intervals measured in ms, not s, especially during testing. That is,
something like getTimeMillis(key, defaultMs).
> 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: Bug
> 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)
