You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (JIRA)" <ji...@apache.org> on 2017/08/15 10:09:00 UTC
[jira] [Created] (FLINK-7451) Query fails when non-ascii characters
are used in string literals
Jark Wu created FLINK-7451:
------------------------------
Summary: 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)