[ 
https://issues.apache.org/jira/browse/FLINK-26355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497923#comment-17497923
 ] 

luoyuxia commented on FLINK-26355:
----------------------------------

[~zoucao] HiveTableSqlFunction  is deprecated. I think the better way is 
waiting [FLINK-26364|https://issues.apache.org/jira/browse/FLINK-26364]  ready.
Hopefully I'll fix it when I'm free. 
Yes, we should consider about compatibility for backporting. But I'm not sure 
what's your concern the about backforward compatibility as it seems won't bring 
any bother about backforward compatibility. Would you like to explain more in 
case I miss some thing.

> 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)

Reply via email to