ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-10732) Incorrect file.encoding leads to inconsistent SqlFieldsQuery results between nodes
Date Sat, 29 Dec 2018 13:12:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-10732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ilya Kasnacheev reassigned IGNITE-10732:
----------------------------------------

    Assignee: Ilya Kasnacheev

> Incorrect file.encoding leads to inconsistent SqlFieldsQuery results between nodes
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-10732
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10732
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.4
>            Reporter: Ilya Kasnacheev
>            Assignee: Ilya Kasnacheev
>            Priority: Critical
>              Labels: windows
>
> When doing 
> {code}
> cache.query(new SqlFieldsQuery("SELECT _key FROM Cache"))
> {code}
> resulting Unicode values may be different when coming from Windows or Linux node.
> Linux nodes will mostly use UTF-8 but Windows nodes will use local CpNNNN encoding to
encode query results, as bizzare as it may sound.
> Windows < - > Windows and Linux < - > Linux will get correct result but Windows
< - > Linux will get broken strings.
> Note that if cluster has Windows and Linux nodes and cache is REPLICATED, results will
be different for subsequent queries!
> There is a workaround for this: set -Dfile.encoding=UTF-8 JVM arg on Windows.
> There is probably an underlying problem in H2 but since non-UTF-8 file.encoding is dangerous
(it affects String.getBytes()) I think we should peg it to UTF-8.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message