[
https://issues.apache.org/jira/browse/HBASE-18642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139314#comment-16139314
]
stack commented on HBASE-18642:
-------------------------------
Thanks [~davelatham] We should put this out on dev for discussion. Idea is
shake out cases where folks are doing setTimestamp. What you doing with it?
We were thinking of returning the internal (opaque) long that hbase stamped the
edit with for clients to read and associate with the transaction id they got
from a Transaction Manager. Would such a thing work for you lot? Is it Omid
that you are running? Thanks D.
> Deprecate setting of timestamp in client for HLC
> ------------------------------------------------
>
> Key: HBASE-18642
> URL: https://issues.apache.org/jira/browse/HBASE-18642
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Amit Patel
> Assignee: Amit Patel
> Priority: Minor
>
> With using [HBASE-14070|https://issues.apache.org/jira/browse/HBASE-14070],
> clients should no longer set the timestamp for mutations (i.e., put/delete)
> because the server will do time stamping instead. Therefore we should look
> into deprecating setTimestamp as well as other methods that allow clients to
> set timestamps.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
