I see KYLIN-3746 is created for it. Thank you for the reporting! Best regards,
Shaofeng Shi 史少锋 Apache Kylin PMC Work email: [email protected] Kyligence Inc: https://kyligence.io/ Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html Join Kylin user mail group: [email protected] Join Kylin dev mail group: [email protected] 梅振楠 <[email protected]> 于2018年12月28日周五 上午11:47写道： > Hi shao feng, > > Today, I tried the purely column, the result is right . > I create a column, comment is the “case when” expression . > > so i think this is a bug. > > i will create a new JIRA for this . > > Best regards. > > > 在 2018年12月28日，上午9:13，ShaoFeng Shi <[email protected]> 写道： > > Hi zhen nan, > > Recently there are several bug reporting about the limit pushdown, as the > following: > > https://issues.apache.org/jira/browse/KYLIN-2841 > https://issues.apache.org/jira/browse/KYLIN-3722 > > The fix is to disable limit pushdown for the unmatched cases. But this > looks like a new case: group by an expression. Could you try to change the > "case when" expression to purely the column? In the meanwhile, please > create a new JIRA for this. Thanks! > > Best regards, > > Shaofeng Shi 史少锋 > Apache Kylin PMC > Work email: [email protected] > Kyligence Inc: https://kyligence.io/ > > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html > Join Kylin user mail group: [email protected] > Join Kylin dev mail group: [email protected] > > > > > 梅振楠 <[email protected]> 于2018年12月27日周四 下午8:36写道： > >> hi all, >> >> i search two times, the sql is same ,but the limit is different . >> one time use the limit ,the other is not >> >> <PastedGraphic-1.png> >> >> >> >> >> and this time is not limit >> >> >> <PastedGraphic-3.png> >> >> >> >> the result is different . >> >> why ? >> >> >> >> >
