[
https://issues.apache.org/jira/browse/KYLIN-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382414#comment-15382414
]
Shaofeng SHI commented on KYLIN-1890:
-------------------------------------
Considering that Cubes can be migrated from one Kylin env to another, using
different table prefixs may not solve the problem. Of course, if the table
name can be changed automatically during the migration, that is acceptable.
> 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)
