[
https://issues.apache.org/jira/browse/HIVE-12207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksei S updated HIVE-12207:
-----------------------------
Attachment: HIVE-12207.patch
The reason for the issue is that calcite uses latin encoding ('ISO-8859-1') by
default. In order to pass non-latin characters they need to be converted to
NlsString with explicit encoding set.
> Query fails when non-ascii characters are used in string literals
> -----------------------------------------------------------------
>
> Key: HIVE-12207
> URL: https://issues.apache.org/jira/browse/HIVE-12207
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Aleksei S
> Assignee: Aleksei S
> Attachments: HIVE-12207.patch
>
>
> While debugging HIVE-11721 I found that using non-ascii characters in string
> literals causes calcite planner to throw the following exception:
> {code}
> 2015-10-17T23:07:20,586 ERROR [main]: parse.CalcitePlanner
> (CalcitePlanner.java:genOPTree(292)) - CBO failed, skipping CBO.
> org.apache.calcite.runtime.CalciteException: Failed to encode 'Абвгде' in
> character set 'ISO-8859-1'
> {code}
> The query is:
> {code}
> select concat("Абвгде", "谢谢") from src limit 1;
> {code}
> Other queries with non-ascii literals fail as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
