[
https://issues.apache.org/jira/browse/KAFKA-12872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-12872:
--------------------------------
Description:
Message format v2 was introduced in Apache Kafka 0.11.0 (released in June 2017)
via
[KIP-98|https://cwiki.apache.org/confluence/display/KAFKA/KIP-98+-+Exactly+Once+Delivery+and+Transactional+Messaging#KIP98ExactlyOnceDeliveryandTransactionalMessaging-MessageFormat]
and has been the default since. It includes a number of enhancements
(partition leader epoch, sequence ids, producer ids, record headers) required
for correctness
([KIP-101|https://cwiki.apache.org/confluence/display/KAFKA/KIP-101+-+Alter+Replication+Protocol+to+use+Leader+Epoch+rather+than+High+Watermark+for+Truncation],
[KIP-279|https://cwiki.apache.org/confluence/display/KAFKA/KIP-279%3A+Fix+log+divergence+between+leader+and+follower+after+fast+leader+fail+over],
[KIP-320|https://cwiki.apache.org/confluence/display/KAFKA/KIP-320%3A+Allow+fetchers+to+detect+and+handle+log+truncation]),
stronger semantics (idempotent producers, transactional clients) and other
features ([KIP-82 - Add Record
Headers|https://cwiki.apache.org/confluence/display/KAFKA/KIP-82+-+Add+Record+Headers],
[KIP-392: Allow consumers to fetch from closest
replica|https://cwiki.apache.org/confluence/display/KAFKA/KIP-392%3A+Allow+consumers+to+fetch+from+closest+replica]).
Four years later, it's time to sunset message formats v0 and v1 to establish a
new baseline in terms of supported client/broker behavior and to improve
maintainability & supportability of Kafka. This also aligns with
[KIP-679|https://cwiki.apache.org/confluence/display/KAFKA/KIP-679%3A+Producer+will+enable+the+strongest+delivery+guarantee+by+default],
which will enable the idempotent producer by default in Apache Kafka 3.0 (and
requires message format v2). We propose the deprecation of message formats v0
and v1 in Apache Kafka 3.0 and their removal in Apache Kafka 4.0.
KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1
> KIP-724: Drop support for message formats v0 and v1
> ---------------------------------------------------
>
> Key: KAFKA-12872
> URL: https://issues.apache.org/jira/browse/KAFKA-12872
> Project: Kafka
> Issue Type: Bug
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Priority: Major
>
> Message format v2 was introduced in Apache Kafka 0.11.0 (released in June
> 2017) via
> [KIP-98|https://cwiki.apache.org/confluence/display/KAFKA/KIP-98+-+Exactly+Once+Delivery+and+Transactional+Messaging#KIP98ExactlyOnceDeliveryandTransactionalMessaging-MessageFormat]
> and has been the default since. It includes a number of enhancements
> (partition leader epoch, sequence ids, producer ids, record headers) required
> for correctness
> ([KIP-101|https://cwiki.apache.org/confluence/display/KAFKA/KIP-101+-+Alter+Replication+Protocol+to+use+Leader+Epoch+rather+than+High+Watermark+for+Truncation],
>
> [KIP-279|https://cwiki.apache.org/confluence/display/KAFKA/KIP-279%3A+Fix+log+divergence+between+leader+and+follower+after+fast+leader+fail+over],
>
> [KIP-320|https://cwiki.apache.org/confluence/display/KAFKA/KIP-320%3A+Allow+fetchers+to+detect+and+handle+log+truncation]),
> stronger semantics (idempotent producers, transactional clients) and other
> features ([KIP-82 - Add Record
> Headers|https://cwiki.apache.org/confluence/display/KAFKA/KIP-82+-+Add+Record+Headers],
> [KIP-392: Allow consumers to fetch from closest
> replica|https://cwiki.apache.org/confluence/display/KAFKA/KIP-392%3A+Allow+consumers+to+fetch+from+closest+replica]).
> Four years later, it's time to sunset message formats v0 and v1 to establish
> a new baseline in terms of supported client/broker behavior and to improve
> maintainability & supportability of Kafka. This also aligns with
> [KIP-679|https://cwiki.apache.org/confluence/display/KAFKA/KIP-679%3A+Producer+will+enable+the+strongest+delivery+guarantee+by+default],
> which will enable the idempotent producer by default in Apache Kafka 3.0
> (and requires message format v2). We propose the deprecation of message
> formats v0 and v1 in Apache Kafka 3.0 and their removal in Apache Kafka 4.0.
>
> KIP:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
