You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Vitalii Diravka (JIRA)" <ji...@apache.org> on 2017/05/03 17:20:05 UTC

[jira] [Commented] (DRILL-4039) Query fails when non-ascii characters are used in string literals

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

Vitalii Diravka commented on DRILL-4039:
----------------------------------------

[~llystar] Looks like your fix is correct. Therefore go ahead and open a pull request against the GitHub mirror (see step 3 from this [guidelines|http://drill.apache.org/docs/apache-drill-contribution-guidelines/#step-3:-get-your-code-reviewed-and-committed-to-the-project]). 
You can find examples of the PR's here: https://github.com/apache/drill/pulls. Please feel free to ask me if you have some questions about the pull request-based review process.

> Query fails when non-ascii characters are used in string literals
> -----------------------------------------------------------------
>
>                 Key: DRILL-4039
>                 URL: https://issues.apache.org/jira/browse/DRILL-4039
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 1.1.0
>         Environment: Linux lnxx64r6 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Sergio Lob
>            Assignee: Vitalii Diravka
>         Attachments: DRILL-4039.patch
>
>
> The following query against DRILL returns this error:
> SYSTEM ERROR: CalciteException: Failed to encode  'НАСТРОЕние' in character set 'ISO-8859-1'
>  cc39118a-cde6-4a6e-a1d6-4b6b7e847b8a on maprd
> Query is:
>     SELECT
>    T1.`F01INT`,
>    T1.`F02UCHAR_10`,
>    T1.`F03UVARCHAR_10`
>     FROM
>    DPRV64R6_TRDUNI01T T1
>     WHERE
>    (T1.`F03UVARCHAR_10` =  'НАСТРОЕние')
>     ORDER BY
>    T1.`F01INT`;
> This issue looks similar to jira HIVE-12207.
> Is there a fix or workaround for this?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)