[
https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594951#comment-13594951
]
Francis Liu commented on HBASE-8015:
------------------------------------
reposting coz of typos:
{quote}
+1 on making core (as opposed to cp-s I assume?)
{quote}
Yes. Making this core would mean I'd have to break the task into cp and core.
CP - for region server groups integration and quota control. Core - for basic
namespace functionality.
{quote}
"Given the level of autonomy namespaces will provide tenants. " what does this
mean?
{quote}
In a security-enabled cluster only system admins can create table, namespaces
will introduce the notion of namespaces admins which will be granted to
tenants. Thus enabling them to create tables themselves.
{quote}
Then, about storing, I suggest not making it part of table name. It seems
brittle, and will limit our options if we want to add features lately due to
backward compat.
{quote}
Having it part of the table name makes the changes less invasive (changes in
meta schema, HTable apis, etc). Though I agree it would be nice to make this
{quote}
Also, how do we handle existing backward compat if someone already has a table
name "foo.bar"?
{quote}
Last I checked '.' around allowed as part of the tablename. The cli will bork
if '.' is used?
{quote}
Will root/meta have to be renamed hbase.root/hbase.meta to be in correct
namespace, and how will it affect current assumptions about sorting if yes?
{quote}
As part of backward compatibility we can skip renaming root and meta and just
explicitly support that they are part of the system namespace? These tables are
already treated differently anyway?
> 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: NamespaceDesign.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
