[
https://issues.apache.org/jira/browse/KYLIN-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billy Liu updated KYLIN-2965:
-----------------------------
Summary: Keep the same cost calculation logic between RealizationChooser
and CubeInstance (was: RealizationChooser cost calculation logic different
with CubeInstance)
> Keep the same cost calculation logic between RealizationChooser and
> CubeInstance
> --------------------------------------------------------------------------------
>
> Key: KYLIN-2965
> URL: https://issues.apache.org/jira/browse/KYLIN-2965
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
> Reporter: Ma Gang
> Assignee: Ma Gang
> Priority: Minor
> Fix For: v2.3.0
>
> Attachments: kylin-2965.patch
>
>
> In RealizationChooser.RealizationCost, it uses cube's all
> dimensions(including all derived columns) to calculate the cost, but in
> CubeInstance, it use row key column count. Think it is a bug, should not
> include the derived column number to calculate cost
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
