[
https://issues.apache.org/jira/browse/KYLIN-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hongbin ma updated KYLIN-1936:
------------------------------
Affects Version/s: v1.5.3
> Improve enable limit logic (exactAggregation is too strict)
> -----------------------------------------------------------
>
> Key: KYLIN-1936
> URL: https://issues.apache.org/jira/browse/KYLIN-1936
> Project: Kylin
> Issue Type: Improvement
> Affects Versions: v1.5.3
> Reporter: hongbin ma
> Assignee: hongbin ma
>
> from zhaotians...@meizu.com:
> recently I got the following error while execute query on a cube which is not
> that big( about 400mb, 20milion record)
> ==================
> Error while executing SQL "select FCRASHTIME,count(1) from
> UXIP.EDL_FDT_OUC_UPLOAD_FILES group by FCRASH_ANALYSIS_ID,FCRASHTIME limit
> 1": Scan row count exceeded threshold: 10000000, please add filter condition
> to narrow down backend scan range, like where clause.
> I guess what it scan were the intermediate result, but It doesn't any order
> by,also the result count is limit to just 1.so it could scan to find any
> record with those two dimension and wala.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
