Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 18 Jun 2013 21:52:20 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12653582.1371592307333.135745.1371592340313@arcas>
In-Reply-To: <JIRA.12653582.1371592307333@arcas>
References: <JIRA.12653582.1371592307333@arcas>
Subject: [jira] [Created] (HBASE-8763) [BRAINSTORM] Combine MVCC and SeqId
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Enis Soztutar created HBASE-8763:
------------------------------------

             Summary: [BRAINSTORM] Combine MVCC and SeqId
                 Key: HBASE-8763
                 URL: https://issues.apache.org/jira/browse/HBASE-8763
             Project: HBase
          Issue Type: Improvement
          Components: regionserver
            Reporter: Enis Soztutar
             Fix For: 0.98.0


HBASE-8701 and a lot of recent issues include good discussions about mvcc + seqId semantics. It seems that having mvcc and the seqId complicates the comparator semantics a lot in regards to flush + WAL replay + compactions + delete markers and out of order puts. 

Thinking more about it I don't think we need a MVCC write number which is different than the seqId. We can keep the MVCC semantics, read point and smallest read points intact, but combine mvcc write number and seqId. This will allow cleaner semantics + implementation + smaller data files. 

We can do some brainstorming for 0.98. We still have to verify that this would be semantically correct, it should be so by my current understanding.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira