[
https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652409#comment-13652409
]
stack commented on HBASE-8015:
------------------------------
Regards sponsoring this issue, would suggest more than [~ted_yu] as volunteer
is needed if serious about getting this in to 0.95/0.96 (I am working on 0.95
testing and last issues so do not have bandwidth to help here)
IMO, the time for new features in 0.95 is loooooonnnnnnggggggg past so hard to
justify holding up release for this.
Lets get a feature branch going. I can help set up apache build of the branch
or do it over on andrew's ec2... so can get some test runs going.
Need to work out the dot problem. Can we do the search in two places as is
suggested over on the list (internally, Elliott has suggested how to
implement); i.e. only new tables go into namespace? (Cannot gauge the
migration problem till know how this plays out)
If this goes into 0.95, table grouping can be done after 0.95 as CPs? Not
clear after reading above.
+1 on getting rid of funky system tables stuff (but yeah, as per Francis above,
they were given the funny names so they sorted before user tables).
Breaking patch into pieces will help yes, especially ones that collect into one
place our interaction with filesystem (see Matteo's recent work).
On the design, needs date, author, and JIRA number.
bq. As a first step we only intend to limit the number of tables and regions a
given namespace may contain.
This can be done later, right? You'd have to do it in hbase.
Are we saying the default ns is called 'default'? Or that it has no name?
bq. NamespaceController coprocessor running on region servers to correctly
enforce quota restrictions
Is this so we can get callbacks on change? (I wish we had in place a general
config. change notification mechanism that this could leverage rather than have
to build its own)
How much of this design has to be in place for 0.96 to ship?
bq. <ROOT>/data/<NAMESPACE>/<TABLE>
Why the need for 'data' in above?
Looking quickly at the attached patch (will look at rb later):
Below is interesting (smile)
{code}
- <hadoop.version>0.23.3</hadoop.version>
+ <hadoop.version>0.23.7-SNAPSHOT</hadoop.version>
{code}
Patch introduces TableName and TableName is used to hold namespace and the name
of the table. NS is a concept superior to tables. It should be elsewhere, in
a NS object? (model seems off).
NamespaceDescriptor implements java Serializable?
NamespaceDesc.. has notion of groups. Is that right given they are add on for
later?
Will look at rb patch next. What is attached doesn't seem enough. Will be
back.
> Support for Namespaces
> ----------------------
>
> Key: HBASE-8015
> URL: https://issues.apache.org/jira/browse/HBASE-8015
> Project: HBase
> Issue Type: New Feature
> Reporter: Francis Liu
> Assignee: Francis Liu
> Attachments: HBASE-8015_draft_94.patch, Namespace Design.pdf
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
