[jira] [Updated] (FLINK-19038) It doesn't support to call Table.limit() continuously

["Yun Gao (Jira)" <ji...@apache.org>]

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

Yun Gao updated FLINK-19038:
----------------------------
    Fix Version/s: 1.16.0

> It doesn't support to call Table.limit() continuously
> -----------------------------------------------------
>
>                 Key: FLINK-19038
>                 URL: https://issues.apache.org/jira/browse/FLINK-19038
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>    Affects Versions: 1.12.0
>            Reporter: Dian Fu
>            Priority: Major
>              Labels: auto-unassigned, pull-request-available
>             Fix For: 1.15.0, 1.16.0
>
>
> For example, table.limit(3).limit(2) will failed with "FETCH is already defined." 
> {code}
> org.apache.flink.table.api.ValidationException: FETCH is already defined.
> 	at org.apache.flink.table.operations.utils.SortOperationFactory.validateAndGetChildSort(SortOperationFactory.java:125)
> 	at org.apache.flink.table.operations.utils.SortOperationFactory.createLimitWithFetch(SortOperationFactory.java:105)
> 	at org.apache.flink.table.operations.utils.OperationTreeBuilder.limitWithFetch(OperationTreeBuilder.java:418)
> {code}
> However, as we support to call table.limit() without specifying the order, I guess this should be a valid usage and should be allowed.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)