flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jark Wu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7451) Query fails when non-ascii characters are used in string literals
Date Tue, 15 Aug 2017 13:42:00 GMT

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

Jark Wu commented on FLINK-7451:
--------------------------------

[~twalthr], is it CALCITE-1903?  It seems that Calcite didn't want to fix it, because it is
not allowed in SQL? 

> Query fails when non-ascii characters are used in string literals
> -----------------------------------------------------------------
>
>                 Key: FLINK-7451
>                 URL: https://issues.apache.org/jira/browse/FLINK-7451
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>            Reporter: Jark Wu
>            Assignee: Jark Wu
>
> I found that using non-ascii characters in string literals causes calcite planner to
throw the following exception:
> {code}
> org.apache.calcite.runtime.CalciteException: Failed to encode '%测试%' in character
set 'ISO-8859-1'
> {code}
> The query is 
> {code}
> SELECT * FROM T WHERE f0 LIKE '%测试%'
> {code}
> The reason for the issue is that calcite uses latin encoding ('ISO-8859-1') by default.
In order to pass non-latin characters we should use unicode encoding as default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message