hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10247) Client promises about timestamps
Date Tue, 12 Aug 2014 00:58:14 GMT

     [ https://issues.apache.org/jira/browse/HBASE-10247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Lars Hofhansl updated HBASE-10247:

    Attachment: 10247-do-not-try-may-eat-your-first-born-v2.txt

Updated patch, again just parking. Disallows Put/Delete according to TSPOLICY, adds tests
for all policies.

* Appends, Increments
* Restrict alters
* Disallow TTL with no wall clock type TSPOLICY

> 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
>             Fix For: 0.99.0, 2.0.0
>         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

View raw message