[
https://issues.apache.org/jira/browse/HBASE-10247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006699#comment-14006699
]
Enis Soztutar commented on HBASE-10247:
---------------------------------------
bq. CLIENT_MONOTONIC? Should be globally unique monotonically increasing
sequence id. Local client guarantee on monotonic is not enough, I think?
Yes, it would mean globally monotonically increasing. Not useful otherwise.
bq. What does mixed mode mean in terms of allowing the server side to make
assumptions about timestamps? Intuitively the answer is none. So this would be
captured by the absence of a table attribute?
Yeah, mixed mode will the same as not declaring anything. Having a state in HTD
is more explicit I think.
> Client promises about timestamps
> --------------------------------
>
> Key: HBASE-10247
> URL: https://issues.apache.org/jira/browse/HBASE-10247
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Lars Hofhansl
> Priority: Minor
>
> This is to start a discussion about timestamp promises declared per table of
> CF.
> For example if a client promises only monotonically increasing timestamps (or
> no custom set timestamps) and VERSIONS=1, we can aggressively and easily
> remove old versions of the same row/fam/col from the memstore before we
> flush, just by supplying a comparator that ignores the timestamp (i.e. two KV
> just differing by TS would be considered equal).
> That would increase the performance of counters significantly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
