[
https://issues.apache.org/jira/browse/FLINK-24754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-24754:
-----------------------------------
Labels: auto-deprioritized-minor pull-request-available (was:
pull-request-available stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-minor, 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.10#820010)
