[
https://issues.apache.org/jira/browse/FLINK-9378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483914#comment-16483914
]
ASF GitHub Bot commented on FLINK-9378:
---------------------------------------
Github user twalthr commented on the issue:
https://github.com/apache/flink/pull/6032
Thanks for the PR @snuyanzin. However, I think we should not change the
exception string but should improve the
`org.apache.flink.api.common.typeinfo.SqlTimeTypeInfo#toString` method instead.
Similar to `org.apache.flink.api.java.typeutils.GenericTypeInfo#toString`. The
type class is too little information. The type information is necessary in most
cases.
> Improve TableException message with TypeName usage
> --------------------------------------------------
>
> Key: FLINK-9378
> URL: https://issues.apache.org/jira/browse/FLINK-9378
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Sergey Nuyanzin
> Assignee: Sergey Nuyanzin
> Priority: Trivial
>
> Currently in TableException simple name is in use. It is not clear what is
> the issue while having error message like {noformat}
> Exception in thread "main" org.apache.flink.table.api.TableException: Result
> field does not match requested type. Requested: Date; Actual: Date
> at
> org.apache.flink.table.api.TableEnvironment$$anonfun$generateRowConverterFunction$1.apply(TableEnvironment.scala:953)
> {noformat}
> or
> {noformat}Caused by: org.apache.flink.table.api.TableException: Type is not
> supported: Date
> at
> org.apache.flink.table.api.TableException$.apply(exceptions.scala:53){noformat}
> also for more detailed have a look at FLINK-9341
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
