[
https://issues.apache.org/jira/browse/KYLIN-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744964#comment-17744964
]
ASF subversion and git services commented on KYLIN-5649:
--------------------------------------------------------
Commit 7a05cfbf4197e7c3fd0ed67dd97e173c83d37ffb in kylin's branch
refs/heads/kylin5_beta from Pengfei Zhan
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=7a05cfbf41 ]
KYLIN-5649 update some spark cache result
> When query contains computed columns, fail to guarantee the priority of using
> the aggregate index to answer the aggregate query
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-5649
> URL: https://issues.apache.org/jira/browse/KYLIN-5649
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 5.0-alpha
> Reporter: Zhiting Guo
> Assignee: Zhiting Guo
> Priority: Major
> Fix For: 5.0-beta
>
> Attachments: When query contains computed columns, fail to guarantee
> the priority of using the aggregate index to answer the aggregate query.pdf
>
>
> After enabling the "kylin.query.use-tableindex-answer-non-raw-query = true" &
> & "kylin.query.layout.prefer-aggindex = true" parameter, the aggregate query
> can match the aggregate index and the basic detail index, but the final hit
> is the basic detail index. What is puzzling is why the aggregate query is
> answered using the basic detail index?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
