You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2020/01/14 12:42:00 UTC
[jira] [Commented] (FLINK-15584) Give nested data type of ROWs in
ValidationException
[ https://issues.apache.org/jira/browse/FLINK-15584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015059#comment-17015059 ]
Jingsong Lee commented on FLINK-15584:
--------------------------------------
Thanks [~BenoitParis] for investigation. FLINK-15546 is a similar problem. Looks like a lot of places need consider print type instead of TypeRoot.
> Give nested data type of ROWs in ValidationException
> ----------------------------------------------------
>
> Key: FLINK-15584
> URL: https://issues.apache.org/jira/browse/FLINK-15584
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 1.9.1, 1.10.0, 1.11.0
> Reporter: Benoît Paris
> Priority: Minor
>
> In
> {code:java}
> INSERT INTO baz_sink
> SELECT
> a,
> ROW(b, c)
> FROM foo_source{code}
> Schema mismatch mistakes will not get proper detail level, yielding the following:
> Caused by: org.apache.flink.table.api.ValidationException: Field types of query result and registered TableSink [baz_sink] do not match.
> Query result schema: [a: Integer, EXPR$2: Row]
> TableSink schema: [a: Integer, payload: Row]
> Leaving the user with an opaque 'Row' type to debug.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)