You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "qstar (JIRA)" <ji...@apache.org> on 2016/12/07 02:15:58 UTC
[jira] [Commented] (KYLIN-1936) Improve enable limit logic
(exactAggregation is too strict)
[ https://issues.apache.org/jira/browse/KYLIN-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727422#comment-15727422 ]
qstar commented on KYLIN-1936:
------------------------------
Hi,there
I use official release binary tar kylin 1.5.4, hbase 0.98.16, the cube(40GB+), when I send sql "select * table_name limit 5" like this, I couldn't get result from kylin, after a while it comes with error saying region is offline, this time hbase didn't crash but no results.I have followed kylin https://issues.apache.org/jira/browse/KYLIN-1787 and https://issues.apache.org/jira/browse/KYLIN-1792, but all won't resolve my problem, please help me work this out
> 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
> Fix For: v1.5.4
>
>
> from zhaotianshuo@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)