You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "mathias kluba (JIRA)" <ji...@apache.org> on 2016/01/06 17:39:40 UTC
[jira] [Commented] (PHOENIX-1966) Support HBase non-default
Namespace
[ https://issues.apache.org/jira/browse/PHOENIX-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085790#comment-15085790 ]
mathias kluba commented on PHOENIX-1966:
----------------------------------------
Not sure that it's duplicated.
We could have 2 Phoenix client (or Query Server) using 2 different namespaces instead of default.
Sure, it's better to fix PHOENIX-1311 and support namespaces directly, but in the mean time, it would be nice to configure the namespace in the hbase-site.xml in the client side.
That allow us to have multiple namespaces with permissions on them, and different clients using Phoenix pointing on these namespaces.
> Support HBase non-default Namespace
> -----------------------------------
>
> Key: PHOENIX-1966
> URL: https://issues.apache.org/jira/browse/PHOENIX-1966
> Project: Phoenix
> Issue Type: New Feature
> Reporter: louis hust
>
> HBase has supported namespace, but phoenix seems just support the "default" namespace, So phoenix should support to specify the non-default namespace on hbase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)