avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AVRO-675) Bytes and fixed setters don't update datum size
Date Thu, 14 Oct 2010 19:21:32 GMT

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

Doug Cutting updated AVRO-675:

    Fix Version/s: 1.4.1
     Hadoop Flags: [Reviewed]

FYI, this unfortunately did not make it into 1.4.0, since no one ever marked its "fix version"
as 1.4.0 or merged it to that branch.  I'll mark it for 1.5.0 now, but if we decide to make
a 1.4.2 release we should include this there.

Committers should always set the "fix-version" when they resolve an issue after committing
a patch.  If the fix version is anything but the next major version that will be branched
from trunk then they also need to merge the change to the intended release branch.

> Bytes and fixed setters don't update datum size
> -----------------------------------------------
>                 Key: AVRO-675
>                 URL: https://issues.apache.org/jira/browse/AVRO-675
>             Project: Avro
>          Issue Type: Bug
>          Components: c
>    Affects Versions: 1.4.0
>            Reporter: Douglas Creager
>             Fix For: 1.4.1
>         Attachments: avro-675.patch
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
> The setter methods for bytes and fixed datum instances don't update the size field. 
So, for instance, if you create a datum:
> {{avro_datum_t  datum = avro_wrapbytes(NULL, 0);}}
> Then later you update that datum to point to a different buffer:
> {{avro_wrapbytes_set(datum, "hello", 5);}}
> If you write that datum out to a file, you'll get a zero-length value in the output,
since the size pointer didn't get updated from 0 to 5.

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

View raw message