[
https://issues.apache.org/jira/browse/HBASE-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544308#comment-14544308
]
Lars Hofhansl commented on HBASE-8927:
--------------------------------------
Perhaps an easier config would be TIMESTAMP_RESOLUTION from a enum with
MILLISECONDS, MICROSECONDS, NANOSECONDS. Default in 0.98, 1.x would be always
MILLISECONDS. In 2.0 old tables default to MILLISECONDS, new tables could
default to MICRO or NANOSECONDS.
Note that we would not actually have this resolution, yet, but rather have
space in the timestamp (by multiplying the current milliseconds by either 1000
or 1000000).
Is that better?
> 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
> Labels: phoenix
> Attachments: 8927.txt
>
>
> Less collisions and we are paying the price of a long anyways so might as
> well fill it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
