[
https://issues.apache.org/jira/browse/CALCITE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084078#comment-16084078
]
Chen Xin Yu edited comment on CALCITE-1886 at 7/12/17 2:42 PM:
---------------------------------------------------------------
Calcite supports
INSERT into db_sink SELECT id,name,price + 1 as price FROM kafka_source +limit
100 offset 10+
But what's expected is :
INSERT into db_sink SELECT id,name,price + 1 as price FROM kafka_source +limit
10, 100 +
was (Author: qihanycx):
Calcite supports
INSERT into db_sink SELECT id,name,price + 1 as price FROM kafka_source +limit
100 offset 10+
But what's expected is :
INSERT into db_sink SELECT id,name,price + 1 as price FROM kafka_source +limit
10, 100 +
> Support LIMIT [offset,] row_count
> ---------------------------------
>
> Key: CALCITE-1886
> URL: https://issues.apache.org/jira/browse/CALCITE-1886
> Project: Calcite
> Issue Type: Improvement
> Reporter: Chen Xin Yu
> Assignee: Julian Hyde
>
> CALCITE support limit offset SQL grammar in CALCITE-43 :
> [LIMIT { count | ALL}]
> [OFFSET start { ROW | ROWS}]
> LIMIT {[offset,] row_count} is also popular used, especially in MySQL, such
> as:
> select * from tableA order by id limit 100,10;
> User should transform the existing sqls until calcite support LIMIT
> {[offset,] row_count}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
