avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiruvalluvan M. G. (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AVRO-383) Optimizing ResolvingDecoder for default values
Date Tue, 02 Feb 2010 05:08:53 GMT

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

Thiruvalluvan M. G. updated AVRO-383:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed revision 905516. Thanks Doug for reviewing.

> Optimizing ResolvingDecoder for default values
> ----------------------------------------------
>                 Key: AVRO-383
>                 URL: https://issues.apache.org/jira/browse/AVRO-383
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Thiruvalluvan M. G.
>            Assignee: Thiruvalluvan M. G.
>         Attachments: AVRO-383-new-test.patch, AVRO-383-new.patch, AVRO-383-test.patch,
> When the reader's and writer's schemas are records and the reader's schema has a field
with default value and the writer's schema doesn't have the field, the ResolvingDecoder keeps
the default value in a byte array. This byte array is in Json format. Moving this to Avro
binary format improves performance.
> Apply the test patch and try "Perf -M". Then apply the patch and run it again. On my
machine, the performance is three times the original.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message