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 Sat, 22 Jun 2013 03:19:20 GMT

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

stack commented on HBASE-8015:

Sorry, meant overload.

bq. But we have production users who are married to the old api and would require them to
upgrade their code to use the new override apis as opposed to a table name change if we recognized
FQTN strings in the existing api. I suspect other users will encounter the same problem.

The argument above is that the current implementation has been deployed some where so the
current implementation is what we have to commit?

Can we figure out something to bring along these legacy folks Francis?  They will have to
restart anyways going to the new stuff?  Can we treat this problem apart from how ns goes
into trunk/0.95?

bq. Essentially what I'm asking is if it would be acceptable to recognize FQTN strings in
the old api alongside implementing override?

How would that work?  How would we distingush a FQTN from a plain TN if the TN has the delimiter
in it as part of its name.  I can see helper methods that the shell or command-line tools
could use but don't see these being run on every tablename we are passed.

bq. What are we buying if we are going to support an external delimiter as well as an internal
delimiter but avoid the old api from recognizing FQTN string?

No conflation of namespace and tablename.  Clean deliniation between the ns and tablename
concepts.  Users can take on the new namespace feature if they want to.  No hackery.

Chatting today, the '/' character came up again.  Did we rule this out as a delimiter?  Yeah
'/' is meaningful in ext and ntfs but can't we leverage their interpretation; e.g. ns is a
directory of tables?  Ditto up in zk.
> 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