You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhiting Guo (Jira)" <ji...@apache.org> on 2023/07/18 08:03:00 UTC

[jira] [Assigned] (KYLIN-5649) When query contains computed columns, fail to guarantee the priority of using the aggregate index to answer the aggregate query

     [ https://issues.apache.org/jira/browse/KYLIN-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhiting Guo reassigned KYLIN-5649:
----------------------------------

    Assignee: Zhiting Guo

> 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-alpha
>
>         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)