You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2017/10/12 08:18:00 UTC

[jira] [Created] (FLINK-7821) Replace Table.limit() by Table.fetch() and Table.offset()

Fabian Hueske created FLINK-7821:
------------------------------------

             Summary: Replace Table.limit() by Table.fetch() and Table.offset()
                 Key: FLINK-7821
                 URL: https://issues.apache.org/jira/browse/FLINK-7821
             Project: Flink
          Issue Type: Improvement
          Components: Table API & SQL
    Affects Versions: 1.4.0
            Reporter: Fabian Hueske
            Assignee: Fabian Hueske
            Priority: Minor


The Table API method limit() exists in two variants:

- {{limit(offset)}} returns all but the first {{offset}} records.
- {{limit(offset, fetch)}} returns {{fetch}} records starting from the {{offset}}'s record.

Especially, the behavior of {{limit(offset)}} is confusing because one would rather expect a behavior of returning the {{offset}} first records instead of all but the {{offset}} first records.

Moreover, the only way to return the first {{x}} records is to specify a {{0}} offset as {{limit(0, x)}}.

I propose to replace both {{limit()}} variants by two new methods {{Table.offset(offset)}} and {{Table.fetch(fetch)}} that can be freely combined:

{code}
table.orderBy(...).fetch(x)
table.orderBy(...).offset(x)
table.orderBy(...).fetch(x).offset(y)
table.orderBy(...).offset(x).fetch(y)
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)