[
https://issues.apache.org/jira/browse/HBASE-18642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139354#comment-16139354
]
Dave Latham commented on HBASE-18642:
-------------------------------------
We use it in multiple ways. A couple use cases first jump to mind:
- For analytics data, we have a table with date tiered compaction enabled. We
set the cell timestamp to represent the timestamp of the data itself. Then
when we run queries on recent data, we can pull only the HFiles with recent
data on them, relying on date tiered compaction to maintain the layout with the
specified cell timestamps.
- For another case, we have certain columns where we want to maintain only the
most recent (or oldest) version of a given cell, according to a timestamp of
the data itself, including data that may arrive to our system late or out of
order. Multiple writes may regularly update that cell, without reading it (or
anything) first. We rely on HBase to surface only the copy with the most up to
date timestamp (or oldest timestamp by inverting it via Long.MAX_VALUE -
timestamp).
> 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)
