[AVRO-1142] Specification is misleading in regards to CRC32 checksum of Snappy blocks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.2
• Component/s: spec
• Assignee: Doug Cutting
• Reporter: Martin Nagy
• Created: 21/Aug/12 13:29
• Updated: 25/Sep/12 21:16
• Resolved: 14/Sep/12 21:09

Description

The specification says:

Each compressed block is followed by its 4-byte, big-endian CRC32 checksum.

This, in my opinion, suggests that the CRC32 checksum is calculated from the compressed block, when in fact it is computed from the block before compression (as it is implemented in java). I've implemented a snappy codec for C++ and had trouble with this