You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Chao Shi (JIRA)" <ji...@apache.org> on 2014/04/04 16:12:16 UTC
[jira] [Resolved] (CRUNCH-368) TupleWritable.Comparator
[ https://issues.apache.org/jira/browse/CRUNCH-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chao Shi resolved CRUNCH-368.
-----------------------------
Resolution: Fixed
Fix Version/s: 0.8.3
0.10.0
Pushed to master and 0.8
> TupleWritable.Comparator
> ------------------------
>
> Key: CRUNCH-368
> URL: https://issues.apache.org/jira/browse/CRUNCH-368
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.10.0, 0.8.3
> Reporter: Chao Shi
> Assignee: Chao Shi
> Fix For: 0.10.0, 0.8.3
>
> Attachments: crunch-368 benchmark.pdf, crunch-368.patch, gen_data.py
>
>
> This patch should improve comparison performance on TupleWritables. It saves the deserialization overhead. It is particularly useful when the input tuple are large, e.g. contains long strings.
> Please note that this changes the binary format of TupleWritable. It adds a var-int indicating size of field after each type code. This is a limitation of the writable system. We do not know the size of each field until fully desalinizing it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)