You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Matt Massie (JIRA)" <ji...@apache.org> on 2010/03/04 03:17:27 UTC
[jira] Resolved: (AVRO-445) avro_size_data() to pre-calculate the
size of an avro_datum_t in serialized form
[ https://issues.apache.org/jira/browse/AVRO-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Massie resolved AVRO-445.
------------------------------
Resolution: Fixed
Thanks for the patch, Bruce. Well written with tests. Nice. Committed to trunk.
> avro_size_data() to pre-calculate the size of an avro_datum_t in serialized form
> --------------------------------------------------------------------------------
>
> Key: AVRO-445
> URL: https://issues.apache.org/jira/browse/AVRO-445
> Project: Avro
> Issue Type: New Feature
> Components: c
> Affects Versions: 1.3.0
> Reporter: Bruce Mitchener
> Assignee: Matt Massie
> Attachments: avro_size.diff
>
>
> I would like to be able to find out how much buffer space will be required to serialize a given avro_datum_t ... I've started implementing this but wanted to get feedback on the general approach and API.
> The details of most of the functions in datum_size.c haven't been updated yet in the attached patch. The rest should be close to working though.
> The main point of concern that I have at the moment is that I'm returning an int64_t which, if positive, is the length required and if negative, will be an error condition (like -EINVAL).
> Thoughts? Anything else in the attached patch that should change?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.