hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8015) Support for Namespaces
Date Fri, 21 Jun 2013 15:52:22 GMT

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

stack commented on HBASE-8015:
------------------------------

The legacy Y! namespacers does compllicate things.  If we are not to unsettle them, the decision
is made already and the override to add NS is out?

This is 0.96.  Y! will have to do a 'migration' to go up on 0.96 anyways?  Can you think of
a 'step' that you could add for Y! cluster that would help here?

Your users are doing 'new HTable(conf, "ns.sometable");' and away they go?

bq. But for the java apis we won't recognize an FQTN string in the public apis?

Well, there would be helper classes for making sense of the FQTN that could be used by shell,
rest, etc., but, yeah, the thought would be that in the API, there is no namepacing, not unless
you ask for it explicitly.

Let me look at the trick for how much we'd have to carry into the future.
                
> 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

Mime
View raw message