You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/12/28 19:03:58 UTC

[jira] [Commented] (HBASE-10247) Client promises about timestamps

    [ https://issues.apache.org/jira/browse/HBASE-10247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15783508#comment-15783508 ] 

stack commented on HBASE-10247:
-------------------------------

For completeness, an obstacle is removed by HBASE-9465 but then a new one presents itself (Client reading and writing against two replicating clusters) courtesy of [~yangzhe1991] comment at https://issues.apache.org/jira/browse/HBASE-17339?focusedCommentId=15780751&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15780751

> 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
>         Attachments: 10247-do-not-try-may-eat-your-first-born-v2.txt, 10247.txt
>
>
> 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.3.4#6332)