[
https://issues.apache.org/jira/browse/AVRO-172?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_10925
]
Matt Massie logged work on AVRO-172:
------------------------------------
Author: Matt Massie
Created on: 26/Oct/09 09:43 PM
Start Date: 26/Oct/09 09:43 PM
Worklog Time Spent: 4h
Issue Time Tracking
-------------------
Time Spent: 4h
Remaining Estimate: 0h (was: 4h)
> Don't include value class data/methods in each instance of a value
> ------------------------------------------------------------------
>
> Key: AVRO-172
> URL: https://issues.apache.org/jira/browse/AVRO-172
> Project: Avro
> Issue Type: Improvement
> Components: c
> Affects Versions: 1.0.0, 1.1.0, 1.2.0
> Reporter: Matt Massie
> Fix For: 1.2.1, 1.3.0
>
> Attachments: AVRO-172.patch
>
> Original Estimate: 4h
> Time Spent: 4h
> Remaining Estimate: 0h
>
> This patch is in response to Thiru's feedback about the current C
> implementation. Thanks, Thiru! I appreciate the feedback.
> Previously, all instances of an Avro value contained class-specific data and
> methods (e.g. callbacks for reading, skipping and writing data). This is
> inefficient and unnecessary.
> This patch creates a per value class registry to hold all class-wide
> information.
> Moreover, this patch creates the framework necessary for support the Avro
> JSON import/export format. Each value class registers all supported data
> formats (named AVRO_BINARY_FORMAT and AVRO_JSON_IMPORT_EXPORT_FORMAT). The
> current JSON parser is a DOM-like parser which is really only suitable for
> process schema data. The callbacks registered in the value class registry
> will allow us to process JSON data in a SAX-link fashion moving forward.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
