[
https://issues.apache.org/jira/browse/SOLR-17154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821276#comment-17821276
]
Tuan Nguyen Huu commented on SOLR-17154:
----------------------------------------
it's a known issue of Calcite
https://issues.apache.org/jira/browse/CALCITE-2616 , which the literal charset
always ISO-8859-1, so it will always throw exception like this:
{code:java}
java.io.IOException: Failed to execute sqlQuery 'SELECT a_s FROM collection1
WHERE a_s LIKE '국문, 國文%'' against JDBC connection 'jdbc:calcitesolr:'.
Caused by: Error while executing SQL "SELECT a_s FROM collection1 WHERE a_s
LIKE '국문, 國文%'": while converting `collection1`.`a_s` LIKE u&'\ad6d\bb38,
\570b\6587%' {code}
A workaround is to override the default charset in Calcite by setting the
*calcite.default.charset* environment property
{code:java}
-Dcalcite.default.charset=UTF-8{code}
> solr jdbc SQL encoding error
> ----------------------------
>
> Key: SOLR-17154
> URL: https://issues.apache.org/jira/browse/SOLR-17154
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
> Affects Versions: 8.11.1
> Reporter: donghwan Lee
> Priority: Major
> Attachments: image-2024-02-07-17-57-30-592.png
>
>
> !image-2024-02-07-17-57-30-592.png|width=889,height=392!
> When connecting to JDBC and writing Korean in SQL, the query is not executed
> because it is input as unicode. However, if it is executed in English, it
> executes normally. Please confirm
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
