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

Vic Wang edited comment on KYLIN-1790 at 6/16/16 7:22 AM:
----------------------------------------------------------

HI, Hongbin

We saw around 70 exception while trying to migrate from 1.4 to 1.5.

2016-06-13 01:54:09,504 ERROR [main CubeDesc:629]: Aggregation group 1 require 
at least 2 dims in a joint
2016-06-13 01:54:09,505 ERROR [main CubeDescManager:207]: Error loading cube 
desc /cube_desc/byr_nps_sm.json
java.lang.IllegalStateException: Aggregation group 1 require at least 2 dims in 
a joint
        at org.apache.kylin.cube.model.CubeDesc.validate(CubeDesc.java:630)
        at org.apache.kylin.cube.model.CubeDesc.init(CubeDesc.java:524)
        at 
org.apache.kylin.cube.CubeDescManager.loadCubeDesc(CubeDescManager.java:134)
        at 
org.apache.kylin.cube.CubeDescManager.reloadAllCubeDesc(CubeDescManager.java:205)
        at org.apache.kylin.cube.CubeDescManager.<init>(CubeDescManager.java:94)
        at 
org.apache.kylin.cube.CubeDescManager.getInstance(CubeDescManager.java:68)
        at 
org.apache.kylin.cube.CubeManager.reloadCubeLocalAt(CubeManager.java:833)
        at 
org.apache.kylin.cube.CubeManager.loadAllCubeInstance(CubeManager.java:820)
        at org.apache.kylin.cube.CubeManager.<init>(CubeManager.java:125)
        at org.apache.kylin.cube.CubeManager.getInstance(CubeManager.java:94)
        at 
org.apache.kylin.cube.upgrade.V1_5_1.CubeMetadataUpgrade_v_1_5_1.upgradeEngineTypeStorageType(CubeMetadataUpgrade_v_1_5_1.java:127)
        at 
org.apache.kylin.cube.upgrade.V1_5_1.CubeMetadataUpgrade_v_1_5_1.upgradeCompatibleMeta(CubeMetadataUpgrade_v_1_5_1.java:71)
        at 
org.apache.kylin.cube.upgrade.common.CubeMetadataUpgrade.upgradeOrVerify(CubeMetadataUpgrade.java:141)
        at 
org.apache.kylin.cube.upgrade.entry.CubeMetadataUpgradeEntry_v_1_5_1.main(CubeMetadataUpgradeEntry_v_1_5_1.java:39)



Any ideas?


was (Author: vic.wang):
HI, Hongbin

We saw around 70 exception while trying to migrate from 1.4 to 1.5.

2016-06-13 01:54:09,504 ERROR [main CubeDesc:629]: Aggregation group 1 require 
at least 2 dims in a joint
2016-06-13 01:54:09,505 ERROR [main CubeDescManager:207]: Error loading cube 
desc /cube_desc/byr_nps_sm.json
java.lang.IllegalStateException: Aggregation group 1 require at least 2 dims in 
a joint
        at org.apache.kylin.cube.model.CubeDesc.validate(CubeDesc.java:630)
        at org.apache.kylin.cube.model.CubeDesc.init(CubeDesc.java:524)
        at 
org.apache.kylin.cube.CubeDescManager.loadCubeDesc(CubeDescManager.java:134)
        at 
org.apache.kylin.cube.CubeDescManager.reloadAllCubeDesc(CubeDescManager.java:205)
        at org.apache.kylin.cube.CubeDescManager.<init>(CubeDescManager.java:94)
        at 
org.apache.kylin.cube.CubeDescManager.getInstance(CubeDescManager.java:68)
        at 
org.apache.kylin.cube.CubeManager.reloadCubeLocalAt(CubeManager.java:833)
        at 
org.apache.kylin.cube.CubeManager.loadAllCubeInstance(CubeManager.java:820)
        at org.apache.kylin.cube.CubeManager.<init>(CubeManager.java:125)
        at org.apache.kylin.cube.CubeManager.getInstance(CubeManager.java:94)
        at 
org.apache.kylin.cube.upgrade.V1_5_1.CubeMetadataUpgrade_v_1_5_1.upgradeEngineTypeStorageType(CubeMetadataUpgrade_v_1_5_1.java:127)
        at 
org.apache.kylin.cube.upgrade.V1_5_1.CubeMetadataUpgrade_v_1_5_1.upgradeCompatibleMeta(CubeMetadataUpgrade_v_1_5_1.java:71)
        at 
org.apache.kylin.cube.upgrade.common.CubeMetadataUpgrade.upgradeOrVerify(CubeMetadataUpgrade.java:141)
        at 
org.apache.kylin.cube.upgrade.entry.CubeMetadataUpgradeEntry_v_1_5_1.main(CubeMetadataUpgradeEntry_v_1_5_1.java:39)


This is the updated metadata for this cube desc:

  "aggregation_groups" : [ {
    "includes" : [ "ATTDNL_BUYER_SGMNTN_DESC", "BUYER_WHO_SELL_YN_IND", 
"BYR_SLR_QSTN_IND", "DEVICE_DMNN_SGMNTN_DESC", "FM_BYR_SGMNTN_DESC", 
"GUEST_YN_IND", "L1_L2_IND", "MONTH_BEG_DT", "PRMRY_BID_CTGRY_PRVS_3M_TXT", 
"PRNT_L1_ID", "QSTN_ID", "QTR_BEG_DT", "REACTVD_BYR_YN_IND", "RPRTD_IND", 
"RPRTD_SGMNT_VAL", "SRVY_TYPE_ID", "TRANCHE_ID", "USER_CNTRY_SITE_CD" ],
    "select_rule" : {
      "hierarchy_dims" : [ ],
      "mandatory_dims" : [ ],
      "joint_dims" : [ [ "BYR_SLR_QSTN_IND", "L1_L2_IND", "PRNT_L1_ID", 
"QSTN_ID", "QTR_BEG_DT", "RPRTD_IND", "SRVY_TYPE_ID", "TRANCHE_ID" ] ]
    }
  }, {
    "includes" : [ "BYR_SLR_QSTN_IND", "L1_L2_IND", "PRNT_L1_ID", "QSTN_ID", 
"QTR_BEG_DT", "RPRTD_IND", "SRVY_TYPE_ID", "TRANCHE_ID" ],
    "select_rule" : {
      "hierarchy_dims" : [ ],
      "mandatory_dims" : [ ],
      "joint_dims" : [ [ "QTR_BEG_DT" ] ]
    }
  } ],

Any ideas?

> Metadata upgrade tool didn't handle aggregation group joint rule successfully
> -----------------------------------------------------------------------------
>
>                 Key: KYLIN-1790
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1790
>             Project: Kylin
>          Issue Type: Bug
>            Reporter: qianqiaoneng
>            Assignee: Vic Wang
>
> If the total dimension is 10, and aggregation group number is 9. after the 
> metadata upgrade, there would be a joint rule with 10-9=1 dimension. But this 
> definition will cause 
> java.lang.IllegalStateException: Aggregation group 0 require at least 2 dims 
> in a joint
> Should change the upgrade logic not to add joint rule if dimension number is 
> 1.



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

Reply via email to