Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6A0D310D8E for ; Tue, 7 Jan 2014 02:25:51 +0000 (UTC) Received: (qmail 48935 invoked by uid 500); 7 Jan 2014 02:25:51 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 48897 invoked by uid 500); 7 Jan 2014 02:25:51 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 48863 invoked by uid 99); 7 Jan 2014 02:25:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jan 2014 02:25:51 +0000 Date: Tue, 7 Jan 2014 02:25:50 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-10288) make mvcc an (optional) part of KV serialization MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HBASE-10288: ------------------------------------- Component/s: HFile > make mvcc an (optional) part of KV serialization > ------------------------------------------------ > > Key: HBASE-10288 > URL: https://issues.apache.org/jira/browse/HBASE-10288 > Project: HBase > Issue Type: Improvement > Components: HFile > Reporter: Sergey Shelukhin > Priority: Minor > > This has been suggested in HBASE-10241. Mvcc can currently be serialized in HFile, but the mechanism is... magical. We might want to make it a part of proper serialization of the KV. It can be done using tags, but we may not want the overhead given that it will be in many KVs, so it might require HFileFormat vN+1. Regardless, the external mechanism would need to be removed while also preserving backward compat. -- This message was sent by Atlassian JIRA (v6.1.5#6160)