You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Prashant Kommireddi (JIRA)" <ji...@apache.org> on 2012/10/30 20:00:12 UTC
[jira] [Commented] (PIG-3017) Pig's object serialization should use
compression
[ https://issues.apache.org/jira/browse/PIG-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487127#comment-13487127 ]
Prashant Kommireddi commented on PIG-3017:
------------------------------------------
Hey Jon, out of curiosity - have you done any comparison between object sizes before and after this patch, and also comparisons w.r.t time? Just trying to understand if Deflater.BEST_COMPRESSION is the ideal choice.
> Pig's object serialization should use compression
> -------------------------------------------------
>
> Key: PIG-3017
> URL: https://issues.apache.org/jira/browse/PIG-3017
> Project: Pig
> Issue Type: Bug
> Reporter: Jonathan Coveney
> Assignee: Jonathan Coveney
> Fix For: 0.12
>
> Attachments: PIG-3017-0.patch
>
>
> We have run into cases of very large JobConf objects, and part of this is the fact that serialized objects are quite large. There is no reason not to use compression here, and ratios should be quite high.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira