[jira] [Commented] (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:comment-tabpanel=16781854#comment-16781854 ] KANG-SEN LU commented on KYLIN-2620: If we have TOPN(SUM(X), GROUP-BY D1) metric configured in a

[jira] [Commented] (KYLIN-3322) TopN requires a SUM to work

[ https://issues.apache.org/jira/browse/KYLIN-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16779823#comment-16779823 ] KANG-SEN LU commented on KYLIN-3322: If the second point is properly handled, then first point is not

[jira] [Commented] (KYLIN-3322) TopN requires a SUM to work

[ https://issues.apache.org/jira/browse/KYLIN-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776848#comment-16776848 ] KANG-SEN LU commented on KYLIN-3322: Hi, Shaofeng:   Thanks for your response. I have two points to

[jira] [Commented] (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:comment-tabpanel=16743363#comment-16743363 ] KANG-SEN LU commented on KYLIN-2620: This bug would limit the selection of topn metric only when the

[jira] [Commented] (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:comment-tabpanel=16743356#comment-16743356 ] KANG-SEN LU commented on KYLIN-2620: I am having doubt in this sentence: "Kylin should check if

[jira] [Commented] (KYLIN-3636) in kylin 2.4.1 and 2.5.1 topn aggregation query caused exception

[ https://issues.apache.org/jira/browse/KYLIN-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691765#comment-16691765 ] KANG-SEN LU commented on KYLIN-3636: Hi, Shaofeng:   I just created a new cube design, the

[jira] [Commented] (KYLIN-3636) in kylin 2.4.1 and 2.5.1 topn aggregation query caused exception

[ https://issues.apache.org/jira/browse/KYLIN-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16688096#comment-16688096 ] KANG-SEN LU commented on KYLIN-3636: I checked my cube design, the engine type is set to 2, i.e. MR.

[jira] [Commented] (KYLIN-3636) in kylin 2.4.1 and 2.5.1 topn aggregation query caused exception

[ https://issues.apache.org/jira/browse/KYLIN-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16688068#comment-16688068 ] KANG-SEN LU commented on KYLIN-3636: Hi, Shaofeng:   I would like to add that there is NO bug in

[jira] [Commented] (KYLIN-3636) in kylin 2.4.1 and 2.5.1 topn aggregation query caused exception

[ https://issues.apache.org/jira/browse/KYLIN-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16688039#comment-16688039 ] KANG-SEN LU commented on KYLIN-3636: Hi, Shaofeng: I believe it is MR, but I am not sure. How do I

[jira] [Commented] (KYLIN-3636) in kylin 2.4.1 and 2.5.1 topn aggregation query caused exception

[ https://issues.apache.org/jira/browse/KYLIN-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16688005#comment-16688005 ] KANG-SEN LU commented on KYLIN-3636: After adding some debugging statements, I found there were two