flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xingcan Cui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-11819) Additional attribute for order by not support by flink sql, but told supported in doc
Date Fri, 15 Mar 2019 12:35:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793592#comment-16793592

Xingcan Cui commented on FLINK-11819:

Hi [~hequn8128] and [~hustclf], sorry for the late reply.

IMO, the current description seems to be OK. However, this could be subjective. If more
readers are confused, we should definitely improve it.

Best, Xingcan

> Additional attribute for order by not support by flink sql, but told supported in doc
> -------------------------------------------------------------------------------------
>                 Key: FLINK-11819
>                 URL: https://issues.apache.org/jira/browse/FLINK-11819
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.7.2
>            Reporter: Lifei Chen
>            Assignee: Lifei Chen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.3
>   Original Estimate: 3h
>          Time Spent: 20m
>  Remaining Estimate: 2h 40m
> I am using flink v1.7.1, when I use flink sql to order by an attribute (not time attribute),
the error logs is as follow.
> sql:
> {quote}"SELECT * FROM events order by tenantId"
> {quote}
> error logs:
> {quote}Exception in thread "main" org.apache.flink.table.api.TableException: Cannot generate
a valid execution plan for the given query:
> FlinkLogicalSort(sort0=[$2], dir0=[ASC])
>  FlinkLogicalNativeTableScan(table=[[_DataStreamTable_0]])
> This exception indicates that the query uses an unsupported SQL feature.
>  Please check the documentation for the set of currently supported SQL features.
>  at org.apache.flink.table.api.TableEnvironment.runVolcanoPlanner(TableEnvironment.scala:377)
>  at org.apache.flink.table.api.TableEnvironment.optimizePhysicalPlan(TableEnvironment.scala:302)
>  at org.apache.flink.table.api.StreamTableEnvironment.optimize(StreamTableEnvironment.scala:814)
>  at org.apache.flink.table.api.StreamTableEnvironment.translate(StreamTableEnvironment.scala:860)
>  at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:305)
>  at org.apache.flink.table.api.java.StreamTableEnvironment.toRetractStream(StreamTableEnvironment.scala:248)
> {quote}
> So as for now, only time attribute is supported by flink for command `order by`, additional
attribute is not supported yet, Is that right ?
> If so, there is a mistake, indicated that other attribute except for `time attribute`
is supported .
> related links: [https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/sql.html#orderby--limit]

This message was sent by Atlassian JIRA

View raw message