You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "liyang (JIRA)" <ji...@apache.org> on 2017/04/17 09:23:41 UTC

[jira] [Commented] (KYLIN-2551) separate table desc by each project

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

liyang commented on KYLIN-2551:
-------------------------------

I'm still not fully convinced this is right way to go -- having one hive table map to possibly multiple table descs in kylin. I can see the benefit, but at same time, the one-to-many relationship feels really odd.

> separate table desc by each project
> -----------------------------------
>
>                 Key: KYLIN-2551
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2551
>             Project: Kylin
>          Issue Type: Improvement
>            Reporter: hongbin ma
>            Assignee: hongbin ma
>
> for some historical reasons different projects share same table desc. This makes project admins having to worry about not to affect cubes in other project.
> The jira aims to separate table desc by each project, and maintain backward compatibility so that users won't have to manually "upgrade"



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)