[
https://issues.apache.org/jira/browse/KYLIN-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783279#comment-16783279
]
ASF subversion and git services commented on KYLIN-2620:
--------------------------------------------------------
Commit f968e31140e6b5e68ef3c8124192987752c32a03 in kylin's branch
refs/heads/master from chao long
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f968e31 ]
KYLIN-2620 Make the condition stricter to answer query with topN
> 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.2
>
>
> 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)
