Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 27 Dec 2013 07:29:57 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12686507.1388129362344.14495.1388129397617@arcas>
In-Reply-To: <JIRA.12686507.1388129362344@arcas>
References: <JIRA.12686507.1388129362344@arcas>
Subject: [jira] [Created] (HBASE-10247) Client promises about timestamps
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Lars Hofhansl created HBASE-10247:
-------------------------------------

             Summary: 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)