[
https://issues.apache.org/jira/browse/FLINK-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9531:
----------------------------------
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.
> Improve logging during type extraction of the Row type
> ------------------------------------------------------
>
> Key: FLINK-9531
> URL: https://issues.apache.org/jira/browse/FLINK-9531
> Project: Flink
> Issue Type: Improvement
> Components: API / Type Serialization System
> Reporter: Timo Walther
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> Users of the Table API in Java will get several warnings about the usage of
> Rows even though the table program is specified correctly.
> {code}
> org.apache.flink.api.java.typeutils.TypeExtractor - class
> org.apache.flink.types.Row is not a valid POJO type
> {code}
> We should improve the user experience here. A correctly defined table program
> should not cause those messages. Users of the row type should rather be
> informed that they have to provide type information manually.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
