You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/07/25 11:06:00 UTC
[jira] [Updated] (KAFKA-4935) Consider disabling record level CRC
checks for message format V2
[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-4935:
-------------------------------
Fix Version/s: (was: 1.0.0)
> Consider disabling record level CRC checks for message format V2
> ----------------------------------------------------------------
>
> Key: KAFKA-4935
> URL: https://issues.apache.org/jira/browse/KAFKA-4935
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Apurva Mehta
> Assignee: Jason Gustafson
> Priority: Blocker
> Labels: exactly-once
> Fix For: 0.11.0.0
>
>
> With the new message format proposed in KIP-98, the record level CRC has been moved to the the batch header.
> Because we expose the record-level CRC in `RecordMetadata` and `ConsumerRecord`, we currently compute it eagerly based on the key, value and timestamp even though these methods are rarely used. Ideally, we'd deprecate the relevant methods in `RecordMetadata` and `ConsumerRecord` while making the CRC computation lazy. This seems pretty hard to achieve in the Producer without increasing memory retention, but it may be possible to do in the Consumer.
> An alternative option is to return the batch CRC from the relevant methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)