hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Navis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8347) Use base-64 encoding instead of custom encoding for serialized objects
Date Mon, 06 Oct 2014 04:30:34 GMT

    [ https://issues.apache.org/jira/browse/HIVE-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159992#comment-14159992
] 

Navis commented on HIVE-8347:
-----------------------------

LGTM, but seemed need a confirmation from hcatalog guys.

> 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 HCATALOG-453.
 The patch for HCATALOG-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)

Mime
View raw message