You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2019/03/01 03:36:00 UTC
[jira] [Assigned] (KYLIN-2620) Check for "ORDER BY LIMIT" clause
when rewrite SUM query as TOPN
[ https://issues.apache.org/jira/browse/KYLIN-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaofeng SHI reassigned KYLIN-2620:
-----------------------------------
Assignee: Chao Long (was: Shaofeng SHI)
> Check for "ORDER BY LIMIT" clause when rewrite SUM query as TOPN
> ----------------------------------------------------------------
>
> Key: KYLIN-2620
> URL: https://issues.apache.org/jira/browse/KYLIN-2620
> Project: Kylin
> Issue Type: Bug
> Components: Measure - TopN
> Reporter: Lin Tingmao
> Assignee: Chao Long
> Priority: Major
> Fix For: v2.6.1
>
>
> When running the following query
> select sum(measure) from table group by col_id
> if there exists TOPN(measure, group by col_id) measure, TopNMeasureType.isTopNCompatibleSum() will pass, so the SUM is rewritten to TOPN. This confuses the user since they may expect a accurate result for every distinct value of group by column(s).
> Kylin should check if "ORDER BY col_id LIMIT topncapacity" is present in the query to determine whether to rewrite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)