You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2012/09/13 21:41:08 UTC
[jira] [Commented] (AVRO-1142) Specification is misleading in
regards to CRC32 checksum of Snappy blocks
[ https://issues.apache.org/jira/browse/AVRO-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455175#comment-13455175 ]
Doug Cutting commented on AVRO-1142:
------------------------------------
Sorry for the confusion this created!
How would you propose we better say this? Perhaps, "followed by the 4-byte, big-endian CRC32 checksum of the uncompressed block"?
> Specification is misleading in regards to CRC32 checksum of Snappy blocks
> -------------------------------------------------------------------------
>
> Key: AVRO-1142
> URL: https://issues.apache.org/jira/browse/AVRO-1142
> Project: Avro
> Issue Type: Bug
> Components: spec
> Reporter: Martin Nagy
>
> 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 :(
--
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