avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1366) Avro 1.7.5 specification description of Object Container Files Metadata is wrong
Date Thu, 12 Sep 2013 23:35:51 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766014#comment-13766014
] 

Hudson commented on AVRO-1366:
------------------------------

SUCCESS: Integrated in AvroJava #397 (See [https://builds.apache.org/job/AvroJava/397/])
AVRO-1366. Fix specification's description of metadata format. (cutting: rev 1522739)
* /avro/trunk/CHANGES.txt
* /avro/trunk/doc/src/content/xdocs/spec.xml

                
> Avro 1.7.5 specification description of Object Container Files Metadata is wrong
> --------------------------------------------------------------------------------
>
>                 Key: AVRO-1366
>                 URL: https://issues.apache.org/jira/browse/AVRO-1366
>             Project: Avro
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: 1.7.5
>         Environment: http://avro.apache.org/docs/current/spec.html
>            Reporter: John McHugh
>            Assignee: Doug Cutting
>              Labels: documentation, patch
>             Fix For: 1.7.6
>
>         Attachments: AVRO-1366.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the documentation, the metadata is described as
> "File metadata consists of:
>    A long indicating the number of metadata key/value pairs.
>    For each pair, a string key and bytes value."
> In fact, the metadata appears to be a map.  If this is the case, the description should
be something like.
> "File metadata is represented by an Avro map coded as a series of blocks where each block
consists of:
>    A long indicating the number of metadata map key/value pairs in the block.
>    For each pair, a string key and bytes value.
> A long value of zero following a block indicates that there are no more blocks in the
map."
> Attempting to process the metadata using the existing specification results in an unexplained
0 byte following the last bytes value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message