Thanks for reporting the bug. These small contributions together make Kylin better. :-)
On Mon, Sep 11, 2017 at 7:51 AM, Mu Kong <kong.mu....@gmail.com> wrote: > Hi, Yang, > > Thanks for your response! > I've already opened an issue here: > https://issues.apache.org/jira/browse/KYLIN-2841 > Thank you for your support! > > Best regards, > Mu > > On Sun, Sep 10, 2017 at 5:05 PM, Li Yang <liy...@apache.org> wrote: > > > Seems a bug in limit handling. Could you open a JIRA to describe the > > problem? > > > > On Mon, Sep 4, 2017 at 1:43 PM, Mu Kong <kong.mu....@gmail.com> wrote: > > > > > Hi all, > > > > > > The previous email seems to be blocked. So I'm re-send this email. > > > I was running a group by query with subquery. Something like the > follows: > > > > > > SELECT > > > SUM(col3) AS col4, > > > SUM(col5) AS total_col5, > > > col1 > > > FROM > > > ( > > > SELECT > > > col1, > > > col2, > > > MAX(col3) AS col3, > > > COUNT(*) AS col5 > > > FROM db.table > > > WHERE col6 = 'somestring' > > > GROUP BY col1, col2 > > > ) > > > GROUP BY col1 > > > > > > When I specify the limit as 50, the result has 19 records, and when I > > > specify the limit as 500000, there are 90+ records in the result and > each > > > record has higher col4 and total_col5. > > > > > > Based on this phenomenon, does it mean the limit in the UI doesn't > limit > > > the number of the record of the query result, but the number of records > > > that are queried against? > > > > > > Best regards, > > > Mu > > > > > >
