Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CE4022004A1 for ; Wed, 9 Aug 2017 18:30:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CD1F1169807; Wed, 9 Aug 2017 16:30:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 10E53169802 for ; Wed, 9 Aug 2017 18:30:08 +0200 (CEST) Received: (qmail 68385 invoked by uid 500); 9 Aug 2017 16:30:08 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 68354 invoked by uid 99); 9 Aug 2017 16:30:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2017 16:30:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B1051180858 for ; Wed, 9 Aug 2017 16:30:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Ek-BIYIHroBR for ; Wed, 9 Aug 2017 16:30:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 91C1661B5B for ; Wed, 9 Aug 2017 16:30:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 95063E0E9A for ; Wed, 9 Aug 2017 16:30:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 65E83241BD for ; Wed, 9 Aug 2017 16:30:02 +0000 (UTC) Date: Wed, 9 Aug 2017 16:30:02 +0000 (UTC) From: "Andrey Kuznetsov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-5655) Introduce pluggable string encoder/decoder MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 09 Aug 2017 16:30:10 -0000 [ 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 (v6.4.14#64029)