Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 17 May 2016 11:37:13 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12969938.1463387821000.208703.1463485033124@Atlassian.JIRA>
In-Reply-To: <JIRA.12969938.1463387821000@Atlassian.JIRA>
References: <JIRA.12969938.1463387821000@Atlassian.JIRA> <JIRA.12969938.1463387821783@arcas>
Subject: [jira] [Updated] (IGNITE-3139) .NET: UTF-16 surrogate symbols are
 not serialized properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 17 May 2016 11:37:14 -0000


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

Vladimir Ozerov updated IGNITE-3139:
------------------------------------
    Fix Version/s:     (was: 1.6)

> .NET: UTF-16 surrogate symbols are not serialized properly
> ----------------------------------------------------------
>
>                 Key: IGNITE-3139
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3139
>             Project: Ignite
>          Issue Type: Bug
>          Components: platforms
>    Affects Versions: 1.5.0.final
>            Reporter: Denis Magda
>            Assignee: Vladimir Ozerov
>             Fix For: 1.7
>
>
> There is an issue with serialization of a surrogate symbol with {{BinaryMarshaller}}. On Java side String's serialization logic was improved to support all the cases. Refer to IGNITE-3098.
> .Net serialization logic has to be updated as well. Please refer to the algorithm located in ignite-3098 branch in the following places:
> - {{BinaryUtils.utf8BytesToStr}} - serialization
> - {{BinaryUtils.strToUtf8Bytes}} - deserialization
> - {{IgniteSystemProperties.IGNITE_BINARY_MARSHALLER_USE_STRING_SERIALIZATION_VER_2}} controls which version of serialization logic to use (old or new).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)