You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Billy(Yiming) Liu (JIRA)" <ji...@apache.org> on 2016/11/09 07:03:58 UTC

[jira] [Commented] (KYLIN-2168) changes on cube-level-config will cause cube inconsistency

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

Billy(Yiming) Liu commented on KYLIN-2168:
------------------------------------------

I could reproduce this issue. First build the cube, then disable and purge. 
Then edit one existing measure, such add more groupby column in TopN measure, it has "Inconsistent cube desc signature for CubeDesc"

> changes on cube-level-config will cause cube inconsistency
> ----------------------------------------------------------
>
>                 Key: KYLIN-2168
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2168
>             Project: Kylin
>          Issue Type: Bug
>            Reporter: hongbin ma
>            Assignee: hongbin ma
>
> some configs will cause cube inconsistence, for example "kylin.cube.aggrgroup.max.combination" and "kylin.cube.aggrgroup.max.size" . The changes on such configurations should be reflected in the signature of cubedesc. The issue becomes more serious as we allowed configuration changes for READY cubes(KYLIN-2090)



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