[
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-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.
> 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: Major
> Labels: auto-unassigned, stale-major
>
> 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.3.4#803005)
