You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Aroop Maliakkal (JIRA)" <ji...@apache.org> on 2015/09/30 06:17:04 UTC

[jira] [Commented] (KYLIN-224) Leverage HBase Namespace to isolate Kylin HTables

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

Aroop Maliakkal commented on KYLIN-224:
---------------------------------------

Why Kylin can't create tables on namespace if the config has a namespace value given ? Currently anyway, kylin user will have  'RWCX' on the cluster . So if we provide namespace name provided on the config, should it be as simple as calling all hbase tables with "$NS:$table_name" instead of calling "$table_name" which is done currently ?

What HBASE-9206 does it that, it will enables the admins to provides these permissions ( RWCX ) restricting to the namespace. Would like to understand if there is any other blockers which is stopping this implementation.



> Leverage HBase Namespace to isolate Kylin HTables 
> --------------------------------------------------
>
>                 Key: KYLIN-224
>                 URL: https://issues.apache.org/jira/browse/KYLIN-224
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Storage - HBase
>            Reporter: Luke Han
>              Labels: github-import
>             Fix For: Backlog
>
>
> To well manage and isolate Kylin relative htable in HBase, using namespace is best way to isolate with other application's tables. 
> Due to [HBASE-9206|https://issues.apache.org/jira/browse/HBASE-9206], Kylin do not support HBase namespace yet.
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/KylinOLAP/Kylin/issues/281
> Created by: [lukehan|https://github.com/lukehan]
> Labels: enhancement, 
> Milestone: Backlog
> Created at: Fri Dec 26 14:05:42 CST 2014
> State: open



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)