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

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-24754:
-----------------------------------
    Labels: pull-request-available stale-minor  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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
>            Priority: Minor
>              Labels: pull-request-available, stale-minor
>
> 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.10#820010)