[
https://issues.apache.org/jira/browse/KYLIN-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382310#comment-15382310
]
hongbin ma commented on KYLIN-1890:
-----------------------------------
it's a good idea.
besides this solution, kylin will also attach a tag to each created htable.
(check the htable's HTableDescriptor, entry "KYLIN_HOST") The tag will be the
metadata store name:
/**
* For each cube htable, we leverage htable's metadata to keep track of
* which kylin server(represented by its kylin_metadata prefix) owns this
htable
*/
public final static String HTableTag = "KYLIN_HOST";
> support hbase table prefix configurable
> ---------------------------------------
>
> Key: KYLIN-1890
> URL: https://issues.apache.org/jira/browse/KYLIN-1890
> Project: Kylin
> Issue Type: Improvement
> Components: General
> Affects Versions: v1.5.2
> Reporter: fengYu
> Assignee: fengYu
> Attachments:
> 0001-KYLIN-1890-support-hbase-table-prefix-configurable.patch
>
>
> some times we need deploy two kylin env based on same hbase, I want to change
> hbase table name prefix based two reasons:
> 1、different kylin env will generate the same table name
> 2、while clean invalid htable for one env will cause delete all tables belong
> to another env.
> different kylin env use different namespace is acceptable either.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
