hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8015) Support for Namespaces
Date Fri, 12 Jul 2013 02:34:49 GMT

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

Francis Liu commented on HBASE-8015:

I had a chat with Stack yesterday to iron out some design details. Here's a quick summary
of things:

1. We will be going with ':' as the delimiter. We'll make it so that the tableNames stored
on the filesystem don't get stored fully-qualified. So that leaves HFileLinks which needs
table names to be written with the namespace.

2. a TableName POJO will be the class that gets passed around where a tableName reference
is needed. HTable and HBaseAdmin will have the old apis overloaded with new apis that accept
the TableName pojo. In addition, the old apis will recognize fully qualified table names.
This keeps symmetry between both apis. Having colon as a delimiter will guarantee there is
no confusion and clear intent.

3. Since we will be using a TableName pojo everywhere internally. That means all the coprocessor
hooks that have tableNames will change as well. This will break backward compatibility.
4. External interfaces REST, Thrift and CLI will not require significant changes as tables
can be referenced using fully-qualified. We will have to add namespace CRUD apis to REST and
Thrift at a latter point.

5. In a separate patch remove '.' prefix in non-table dirs in root dir

> 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

View raw message