hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-42) Set region split size on table creation
Date Sun, 08 Jun 2008 16:51:45 GMT

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

Andrew Purtell commented on HBASE-42:
-------------------------------------

Preliminary patch attached. (Sorry for the delay, just back from Asia...) 

Todo:

* Update migration script to rewrite HTableDescriptor with version tag.
* Test case.
* Consider extending "modifyTableMeta" to be a single point for changing all HTable metadata,
with corresponding change to HMasterInterface to remove addColumn, deleteColumn, and similar.
This wouldn't make much difference on the server side but on the client side having a single
RPC through which all table metadata is changed would make it easier to move at some later
time to Zookeeper or whatever is chosen. Probably the easiest thing to do is something like
the following:
*# Client disables table.
*# Client uses RPC to retrieve a lease and a serialized HTableDescriptor from the HMaster,
which is instantiated. If another lease is outstanding, client must retry. 
*# Client manipulates the HTableDescriptor via its methods.
*# Client uses RPC to send the updated HTableDescriptor to the HMaster.
*# Master records the updated HTableDescriptor.
*# Client enables table.


> Set region split size on table creation
> ---------------------------------------
>
>                 Key: HBASE-42
>                 URL: https://issues.apache.org/jira/browse/HBASE-42
>             Project: Hadoop HBase
>          Issue Type: New Feature
>            Reporter: Paul Saab
>            Assignee: Andrew Purtell
>            Priority: Minor
>         Attachments: hbase-regionsize-0.2-r664521.patch
>
>
> Right now the region size before a split is determined by a global configuration.  It
would be nice to configure tables independently of the global parameter.

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


Mime
View raw message