[
https://issues.apache.org/jira/browse/HDFS-9847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207712#comment-15207712
]
Lin Yiqun commented on HDFS-9847:
---------------------------------
Update a new patch with nothrow way, and it will print log info when the value
are lossing precision. Also I fixed the minor of lossing precision info in my
patch. I tested in my local, print like this:
{code}
Loss of precision converting 7s to MINUTES for test.time.a
{code}
[~arpitagarwal], [~chris.douglas], I think this is a better way, what do you
think, pengding jenkins.
> 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-nothrow.001.patch, HDFS-9847.001.patch,
> HDFS-9847.002.patch, HDFS-9847.003.patch, HDFS-9847.004.patch,
> HDFS-9847.005.patch, HDFS-9847.006.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)
