[
https://issues.apache.org/jira/browse/HBASE-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708861#comment-13708861
]
stack commented on HBASE-8927:
------------------------------
bq. ...with the exception of column timestamp precision, for which a more
complex and safer scheme can be made as suggested by some comments above, and
measuring time taken for short (normally expected to take single seconds or
less) operations.
Seems like good enough reasons to me for doing nano time.
I took a look at jdk8 and the story is no different there in its description of
system.nanotime. It adds a java.time package with classes like Instant w/ its
nanosecond resolution
http://download.java.net/jdk8/docs/api/java/time/Instant.html but it doesn't
look too amenable given its long of seconds and then nanos inside a second
(apart from it being jdk8)
Could do something like Lars suggests above w/ left shift filling in bottom few
bytes w/ an incrementing number; it'd be a bit of a pain to implement but would
be nice avoiding clashes.
> Use nano time instead of mili time everywhere
> ---------------------------------------------
>
> Key: HBASE-8927
> URL: https://issues.apache.org/jira/browse/HBASE-8927
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Attachments: 8927.txt
>
>
> Less collisions and we are paying the price of a long anyways so might as
> well fill it.
--
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
