You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/09/18 09:13:00 UTC

[jira] [Updated] (IGNITE-5655) Introduce pluggable string encoder/decoder

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

Vladimir Ozerov updated IGNITE-5655:
------------------------------------
    Labels: iep-2  (was: )

> Introduce pluggable string encoder/decoder
> ------------------------------------------
>
>                 Key: IGNITE-5655
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5655
>             Project: Ignite
>          Issue Type: New Feature
>          Components: binary
>    Affects Versions: 2.0
>            Reporter: Valentin Kulichenko
>            Assignee: Andrey Kuznetsov
>              Labels: iep-2
>             Fix For: 2.3
>
>
> Currently binary marshaller encodes strings in UTF-8. However, sometimes it makes sense to serialize strings with different encodings to save space. Let's add global property to control String encoding and customize our binary protocol to support it. For instance, we can add another flag {{ENCODED_STRING}}, which will write strings as follows:
> [flag][encoding_flag][str_len][str_bytes]
> First implementation should set preferred encoding for strings in BinaryConfiguration. This setting is optional, default encoding is UTF-8. Currently, the same BinaryConfiguration is used for all cluster nodes, thus no encoding clashes are possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)