Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Sat, 4 Oct 2014 00:41:33 +0000 (UTC)
From: "Mariappan Asokan (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12745868.1412383047000.188805.1412383293673@Atlassian.JIRA>
In-Reply-To: <JIRA.12745868.1412383047000@Atlassian.JIRA>
References: <JIRA.12745868.1412383047000@Atlassian.JIRA>
 <JIRA.12745868.1412383047498@arcas>
Subject: [jira] [Updated] (HIVE-8347) Use base-64 encoding instead of custom
 encoding for serialized objects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mariappan Asokan updated HIVE-8347:
-----------------------------------
    Attachment: HIVE-8347.patch

Attached a patch


> Use base-64 encoding instead of custom encoding for serialized objects
> ----------------------------------------------------------------------
>
>                 Key: HIVE-8347
>                 URL: https://issues.apache.org/jira/browse/HIVE-8347
>             Project: Hive
>          Issue Type: Improvement
>          Components: HCatalog
>    Affects Versions: 0.13.1
>            Reporter: Mariappan Asokan
>         Attachments: HIVE-8347.patch
>
>
> Serialized objects that are shipped via Hadoop {{Configuration}} are encoded using custom encoding (see {{HCatUtil.encodeBytes()}} and its complement {{HCatUtil.decodeBytes()}}) which has 100% overhead.  In other words, each byte in the serialized object becomes 2 bytes after encoding.  Perhaps, this might be one of the reasons for the problem reported in HIVE-453.  The patch for HIVE-453 compressed serialized {{InputJobInfo}} objects to solve the problem.
> By using Base64 encoding, the overhead will be reduced to about 33%.  This will alleviate the problem for all serialized objects.


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