[
https://issues.apache.org/jira/browse/HBASE-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458419#comment-13458419
]
Lars Hofhansl commented on HBASE-6833:
--------------------------------------
We need to keep in mind then that nanotime does not reflect any absolute time
and is only supposed to be used for time-differences. As long we make sure
it'll only ever used for that, we should be OK.
I.e. we could not take nanotime, and use that for the persistent KV timestamps.
(Going the documentation and what I have read elsewhere)
> [WINDOWS] Java Milisecond precision on Windows
> ----------------------------------------------
>
> Key: HBASE-6833
> URL: https://issues.apache.org/jira/browse/HBASE-6833
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 0.96.0, 0.94.3
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Labels: windows
>
> HBase relies on the system clock obtained by System.currentTimeMilis() to
> supply the version, if it is not provided by the client in Put's and
> Delete's. At HBASE-6832 and HBASE-6826, we discovered that on some platforms,
> the milis clock might not be updated every milisecond, which might cause
> unexpected behavior. We also did some preliminary analysis there.
> In this issue, we can further discuss and inspect whether it is a problem for
> main target platforms and if so what can be done.
--
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
