[
https://issues.apache.org/jira/browse/HBASE-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219860#comment-14219860
]
Lars Hofhansl commented on HBASE-8927:
--------------------------------------
Should we pick this up again?
bq. At a minimum, I think we should just left shift millis so we open up the
lower bytes for external transactions, etc. to use, if we do nothing else on
this issue.
Agreed. We'd probably need to add a "timestamp multiplier" or "timestamp shift"
option to table or column family. That way we can grandfather in old tables and
in all cases scale the TTL value accordingly.
I think this is the only concerns, the timestamps never actually have to
changed in the existing/old KVs (even when stored in the WAL). Care would have
to be taken when the multiplier is changed to higher value and there's a TTL on
the table already, that would probably not work easily.
> 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)
