[
https://issues.apache.org/jira/browse/FLINK-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10568:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned 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.
> Show correct time attributes when calling Table.getSchema()
> -----------------------------------------------------------
>
> Key: FLINK-10568
> URL: https://issues.apache.org/jira/browse/FLINK-10568
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Timo Walther
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> A call to `Table.getSchema` can result in false positives with respect to
> time attributes. Time attributes are converted during optimization phase. It
> would be helpful if we could execute parts of the optimization phase when
> calling this method in order to get useful/correct information.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
