You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2021/11/25 14:45:00 UTC

[jira] [Assigned] (FLINK-24754) PushDownSepcs are better to be print by a clear order.

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

Martijn Visser reassigned FLINK-24754:
--------------------------------------

    Assignee: Marios Trivyzas

> PushDownSepcs are better to be print by a clear order.
> ------------------------------------------------------
>
>                 Key: FLINK-24754
>                 URL: https://issues.apache.org/jira/browse/FLINK-24754
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner
>            Reporter: xuyang
>            Assignee: Marios Trivyzas
>            Priority: Minor
>              Labels: pull-request-available
>
> Now, when specs are print (e.g. in the function toString), it depends on the order in which they are added to the table source. But it's unordered now. We'd better print these specs in a clear order.



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