Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.7.5
Description
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.