[ https://issues.apache.org/jira/browse/AVRO-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852951#action_12852951 ]
Scott Banachowski commented on AVRO-498: ---------------------------------------- Yes, in both cases (longs and metadata), I assumed these were the case from the context, but feel the spec could be more explicit about it. > Clarify spec for object container files > --------------------------------------- > > Key: AVRO-498 > URL: https://issues.apache.org/jira/browse/AVRO-498 > Project: Avro > Issue Type: Improvement > Components: spec > Reporter: Scott Banachowski > Attachments: AVRO-498.patch > > > I have some proposed changes for the spec in the Object Container Files > section. > The fixes are: > 1) call out explicitly that when it says long, it means avro-encoded long. > 2) since the implementations are serializing the metadata as an avro map, > this map should be followed by a block size of 0 (consistent with avro map > encoding) > 3) fix the example header schema so it passes JSONLint (it had an extra comma > after the last array value). > Number 2 above is something I'm not sure about, because I don't know if it's > a compatible change... I hope it does not break any implementations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.