[
https://issues.apache.org/jira/browse/KYLIN-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725203#comment-14725203
]
hongbin ma commented on KYLIN-983:
----------------------------------
[~lukehan] it might be a little confusing that we're still using 0.7-staging
but fixed versions being 1.1, any notifications or document required?
> 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: liyang
> Fix For: v0.8.1, v1.1
>
> Attachments: 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)
