[ https://issues.apache.org/jira/browse/FLINK-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337097#comment-17337097 ]
Timo Walther edited comment on FLINK-10568 at 4/30/21, 5:48 AM: ---------------------------------------------------------------- [~Leonard Xu] this is not entirely correct, it can still show false positives because only an optimizer run can figure out whether a attribute looses its properties. I would keep this issue for now. was (Author: twalthr): [~Leonard Xu] this is not entirely correct, it can still show false positives because only an optimizer run can figure out whether a attribute looses it's properties. I would keep this issue for now. > 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 > > 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)