Hi Chia-Ping,

Thanks for pointing those two fields out. I retract my -1.

Cheers,
Anton

Den sön 27 okt. 2024 kl 17:40 skrev Chia-Ping Tsai <chia7...@apache.org>:

> hi Anton
>
> Thanks for sharing your insights on Kafka serialization—it’s really cool
> and interesting to me. Additionally, you inspired me to file a JIRA issue
> (KAFKA-17882) to improve the documentation.
>
> The most important aspect of Kafka is compatibility, and the undocumented
> behavior has been in place for some time [0][1]. This means there’s no need
> to rush your improvement for 3.9, as we’ll need to explicitly add default
> values after applying your patch to ensure we generate the same binary data.
>
> In short, we can improve the documentation first. In the meantime, we can
> continue discussing behavior clarification for 4.0, and RM can keep running
> the RC for 3.9. Everything is on track.
>
> Best,
> Chia-Ping
>
> [0]
> https://github.com/apache/kafka/blob/3.8/clients/src/main/resources/common/message/FetchSnapshotResponse.json#L43
> [1]
> https://github.com/apache/kafka/blob/3.8/group-coordinator/src/main/resources/common/message/ConsumerGroupMemberMetadataValue.json#L39
>
> On 2024/10/27 15:28:05 Anton Agestam wrote:
> > -1, refer to comments on the RC 2 thread.
> >
> > Den sön 27 okt. 2024 kl 02:51 skrev Colin McCabe <cmcc...@apache.org>:
> >
> > > This is the RC5 candidate for the release of Apache Kafka 3.9.0.
> > >
> > > - This is a major release, the final one in the 3.x line. (There may of
> > > course be other minor releases in this line, such as 3.9.1.)
> > > - Tiered storage will be considered production-ready in this release.
> > > - This will be the final major release to feature the deprecated
> ZooKeeper
> > > mode.
> > >
> > > This release includes the following KIPs:
> > > - KIP-853: Support dynamically changing KRaft controller membership
> > > - KIP-1057: Add remote log metadata flag to the dump log tool
> > > - KIP-1049: Add config log.summary.interval.ms to Kafka Streams
> > > - KIP-1040: Improve handling of nullable values in InsertField,
> > > ExtractField, and other transformations
> > > - KIP-1031: Control offset translation in MirrorSourceConnector
> > > - KIP-1033: Add Kafka Streams exception handler for exceptions
> occurring
> > > during processing
> > > - KIP-1017: Health check endpoint for Kafka Connect
> > > - KIP-1025: Optionally URL-encode clientID and clientSecret in
> > > authorization header
> > > - KIP-1005: Expose EarliestLocalOffset and TieredOffset
> > > - KIP-950: Tiered Storage Disablement
> > > - KIP-956: Tiered Storage Quotas
> > >
> > > Release notes for the 3.9.0 release:
> > >
> https://dist.apache.org/repos/dist/dev/kafka/3.9.0-rc5/RELEASE_NOTES.html
> > >
> > > *** Please download, test and vote by October 30, 2024.
> > >
> > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > > https://kafka.apache.org/KEYS
> > >
> > > * Release artifacts to be voted upon (source and binary):
> > > https://dist.apache.org/repos/dist/dev/kafka/3.9.0-rc5/
> > >
> > > * Docker release artifacts to be voted upon:
> > > apache/kafka:3.9.0-rc5
> > > apache/kafka-native:3.9.0-rc5
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc:
> > > https://dist.apache.org/repos/dist/dev/kafka/3.9.0-rc5/javadoc/
> > >
> > > * Documentation:
> > > https://kafka.apache.org/39/documentation.html
> > >
> > > * Protocol:
> > > https://kafka.apache.org/39/protocol.html
> > >
> > > * Tag to be voted upon (off 3.9 branch) is the 3.9.0-rc5 tag:
> > > https://github.com/apache/kafka/releases/tag/3.9.0-rc5
> > >
> > > * Successful Docker Image Github Actions Pipeline for 3.9 branch:
> > > Docker Build Test Pipeline (JVM):
> > > https://github.com/apache/kafka/actions/runs/11535300463
> > > Docker Build Test Pipeline (Native):
> > > https://github.com/apache/kafka/actions/runs/11535328957
> > >
> > > Thanks to everyone who helped with this release candidate, either by
> > > contributing code, testing, or documentation.
> > >
> > > Regards,
> > > Colin
> > >
> >
>

Reply via email to