[
https://issues.apache.org/jira/browse/FLINK-26355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497918#comment-17497918
]
zoucao commented on FLINK-26355:
--------------------------------
I use default dialect with hive module rather than hive dialect. Is it
necessary to fix the varchar type in `HiveTableSqlFunction#coerce` ? or waiting
FLINK-26364 ready. WDYS [~luoyuxia]. If we want to fix it in FLINK-26364, I
think we should consider more about compatibility for backporting.
> VarCharType was not be considered in HiveTableSqlFunction
> ---------------------------------------------------------
>
> Key: FLINK-26355
> URL: https://issues.apache.org/jira/browse/FLINK-26355
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Ecosystem
> Reporter: zoucao
> Priority: Major
>
> VarCharType was not be considered in `HiveTableSqlFunction#coerce`, see
> [link|https://github.com/apache/flink/blob/a7192af8707f3f0d0f30fc71f3477edd92135cac/flink-table/flink-table-planner/src/main/java/org/apache/flink/table/planner/functions/utils/HiveTableSqlFunction.java#L146],
> before invoke `HiveTableSqlFunction#coerce`, flink will call the method
> `createFieldTypeFromLogicalType` to build argumentsArray, if the field's type
> is varchar, the exception will be thrown.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
