[
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-unassigned stale-major (was: auto-unassigned)
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, stale-major
>
> 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.3.4#803005)
