Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <643336261.1255976039424.JavaMail.jira@brutus>
Date: Mon, 19 Oct 2009 18:13:59 +0000 (UTC)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1886) move table and column family
 attributes to ZK to make them live
In-Reply-To: <2075655813.1254708716220.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-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767432#action_12767432 ] 

Jonathan Gray commented on HBASE-1886:
--------------------------------------

I have a few reasons for not wanting this part of branch, though I understand you needing it for internal use.
- This is not a standalone issue... the design of this should be part of the larger master redesign / increased usage of ZK (create/enable/disable tables, region assignment, load balancing, etc)
- Putting this into branch while also moving forward with more changes for trunk could mean a fork in ZK usage between the two
- And strictly speaking, this is a major change, not a major bug, and really doesn't belong in a minor revision

I'd like to expand this conversation to be about all the stuff we want to move into ZK, how we will design our usage of ZK, etc... rather than focusing on this single change.

On the other hand, we haven't had much work done in trunk around this stuff... this could be a good first step.  I just don't want to tie our hands or limit our thinking because we want to put this into branch.

> move table and column family attributes to ZK to make them live
> ---------------------------------------------------------------
>
>                 Key: HBASE-1886
>                 URL: https://issues.apache.org/jira/browse/HBASE-1886
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 0.20.2, 0.21.0
>
>         Attachments: live_attributes.patch
>
>
> This is a first cut at moving table and column family attributes up to ZK where they can be modified any time without requiring a disable/enable table cycle. Adds methods to ZooKeeperWrapper for support server side. Adds methods to HTableInterface for client side access. Client side talks directly to ZK. 
> The new hierarchy for attributes in ZK is like:
> {noformat}
> /hbase
>   /table
>     /<table-name>
>       /attr
>         /<table-attr-name>
>         /<family-name>
>           /<family-attr-name>
> {noformat}
> As before attribute names and values are byte[], but now that they are hosted in ZK, the path delimiter ('/') cannot be used.
> Attached patch compiles but has not been tested. I put it up for a concept review. Next step before this is functional is to deprecate the attribute related methods on HTD and HCD and chase through the warnings to find all users who should be updated to use the ZK wrapper or new HTable methods instead. And, of course, then add test cases that successfully complete.

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