You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "hongbin ma (JIRA)" <ji...@apache.org> on 2015/09/07 04:50:45 UTC

[jira] [Assigned] (KYLIN-983) Query sql offset keyword bug

     [ https://issues.apache.org/jira/browse/KYLIN-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

hongbin ma reassigned KYLIN-983:
--------------------------------

    Assignee: hongbin ma  (was: liyang)

> Query sql offset keyword bug
> ----------------------------
>
>                 Key: KYLIN-983
>                 URL: https://issues.apache.org/jira/browse/KYLIN-983
>             Project: Kylin
>          Issue Type: Bug
>          Components: Query Engine, Storage - HBase
>    Affects Versions: v0.7.2
>            Reporter: Xiaoyu Wang
>            Assignee: hongbin ma
>             Fix For: v2.0, v1.1
>
>         Attachments: KYLIN-983-Query-sql-offset-keyword-bug-V2.patch, KYLIN-983-Query-sql-offset-keyword-bug-V3-0.7-staging-branch.patch, KYLIN-983-Query-sql-offset-keyword-bug-V3-0.8-branch.patch, KYLIN-983-Query-sql-offset-keyword-bug.patch
>
>
> SQL is:
> {code}
> select type,count(*) from test group by type limit 1 offset 10
> {code}
> the resultset size is 0.
> I see the hbase scanner only judge the limit size,not found the offset size.
> The most queries offset is calcite service when the scan count bigger than limit+offset.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)