[
https://issues.apache.org/jira/browse/IGNITE-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-5655:
------------------------------------
Description:
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]
was:
Currently binary marshaller encodes strings in UTF-8. However, sometimes it
makes sense to customize this.
Need to:
# Create {{BinaryStringEncoder}} interface with {{encode}} and {{decode}}
methods that will convert string to byte array and back.
# Create default implementation based on UTF-8.
# Add {{stringEncoder}} configuration property to {{BinaryConfiguration}}.
> 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
> Fix For: 2.1
>
>
> 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]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
