Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1682357922.1216248691632.JavaMail.jira@brutus>
Date: Wed, 16 Jul 2008 15:51:31 -0700 (PDT)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-484) Store HRegionInfo in META and ROOT as
 multiple cells instead of a binary field
In-Reply-To: <842063743.1204409214921.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-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614142#action_12614142 ] 

Jean-Daniel Cryans commented on HBASE-484:
------------------------------------------

I don't think it will be needed anymore. +1 on closing this jira.

> Store HRegionInfo in META and ROOT as multiple cells instead of a binary field
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-484
>                 URL: https://issues.apache.org/jira/browse/HBASE-484
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>            Reporter: Bryan Duxbury
>            Priority: Trivial
>
> Right now we keep our HRegionInfos stored as a stream of bytes in a single column in the META and ROOT tables. This is convenient to build and write in code under normal circumstances, and we've made the shell deserialize the binary into human readable data for display purposes.
> However, we really don't have much flexibility to edit the info through the shell since it's binary. This means that when we need some latitude to reach in and tweak some stuff because of bugs or just for experimental purposes, we have to go and write custom tools in Java to achieve anything.
> One way to mitigate this problem would be to stop storing HRIs as binary data and start putting each field into separate first-class columns in META and ROOT. This would let us do whatever we want in terms of single-row operations in the shell. We wouldn't have to make a special case for reading the data in those circumstances then, either.

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