ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-5655) Introduce pluggable string encoder/decoder
Date Wed, 09 Aug 2017 16:30:02 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120193#comment-16120193

Andrey Kuznetsov edited comment on IGNITE-5655 at 8/9/17 4:29 PM:

[~vozerov], please review my changes.

was (Author: andrey-kuznetsov):
[~devozerov], please review my changes.

> 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
>             Fix For: 2.2
> 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

View raw message