[
https://issues.apache.org/jira/browse/IGNITE-10732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726792#comment-16726792
]
ASF GitHub Bot commented on IGNITE-10732:
-----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/5725
IGNITE-10732 Force -Dfile.encoding=UTF-8
in linux/windows batch runners, C# and C++.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10732
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5725.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5725
----
commit 180abe4ad6b54068075affc6d0d5acff0ccd7936
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-12-21T14:52:21Z
IGNITE-10732 Force -Dfile.encoding=UTF-8 in linux/windows batch runners, C#
and C++.
----
> 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
> 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)
