hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10247) Client promises about timestamps
Date Tue, 31 Dec 2013 00:35:50 GMT

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

Jonathan Hsieh commented on HBASE-10247:
----------------------------------------

My hope actually would be to have MOD_TS_OK=false by default on all newly created tables,
but on by default for any previously existing tables. This way we don't surprise any existing
users unless they create new tables.  Systems like phoenix would create with MOD_TS_OK=true.

If it was on, I think we could legitimately turn on distributed log replay on by default.
 It also would effectively eliminate a class of problems users can encounter if they get fancy
without knowing what really is going one.

> 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.1.5#6160)

Mime
View raw message