Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1003913652.1225150424345.JavaMail.jira@brutus>
Date: Mon, 27 Oct 2008 16:33:44 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-859) HStoreKey needs a reworking
In-Reply-To: <518778454.1220160104394.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-859:
-----------------------------

++1 on it being a Blocker.  We pay for this bigtime looking at hbase under load with a profiler.

> HStoreKey needs a reworking
> ---------------------------
>
>                 Key: HBASE-859
>                 URL: https://issues.apache.org/jira/browse/HBASE-859
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 0.20.0
>
>
> HBASE-832 had to make an ugly hack to address fact that rows that included the delimiter -- or a byte < delimiter -- messed up sorting in .META.  Fix the ugly hack, and while we're at it, add a byte for flags to the HSK so can mark if key is a meta key, a delete key (cell/family/row), etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.