[
https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690489#comment-13690489
]
Francis Liu commented on HBASE-8015:
------------------------------------
{quote}
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?
{quote}
We are not married to the current implementation yet. 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.
Essentially what I'm asking is if it would be acceptable to recognize FQTN
strings in the old api alongside implementing override?
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?
*Nit side note: Shouldn't it be be called overload (not override), since we are
planning on overloading a a method or am I thinking of one of the other
approaches?
> 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
