You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Mariappan Asokan (JIRA)" <ji...@apache.org> on 2014/10/04 02:37:35 UTC

[jira] [Created] (HIVE-8347) Use base-64 encoding instead of custom encoding for serialized objects

Mariappan Asokan created HIVE-8347:
--------------------------------------

             Summary: 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


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)