Log Compaction

Log Compaction | Highlights in the Apache Kafka and Stream Processing Community | October 2016

Gwen Shapira
Last Updated: 

This month the community has been focused on the upcoming release of Apache Kafka 0.10.1.0. Led by the fearless release manager, Jason Gustafson, we voted on a release plan, cut branches and started voting on the first release candidate. Please contribute to the community by downloading the release candidate, testing it out and letting everyone know how it went. If no serious bugs are found, we are hoping to finalize the release by mid-October.

In addition to the vote, we gave our website a quick facelift, contribution of Derrick Or. We appreciated the feedback from the community and issues were quickly addressed.

And as usual, there are several very lively discussions in the community:

  • KIP-74: Proposal to limit not just the amount of data returned by a consumer fetch per partition, but also the amount of data returned for each fetch request overall. This will give users better control over the memory usage of consumers, but even better – this allows consumers to make progress even if a partition contains messages larger than the maximum fetch size. This proposal has been merged and will be part of the 0.10.1.0 release.
  • KIP-79: Proposal to add methods for searching by timestamp to the new consumer was accepted and merged. It will be included in the next release to everyone’s great joy.
  • KIP-82: Proposal for adding headers to Kafka messages. This proposal is very popular because so many organizations are using headers internally. It is also controversial – Kafka project has a long tradition of keeping the message completely unstructured and letting the users and client put whatever structure they need inside the message. Whatever the decision is, it will have serious impact on the Apache Kafka ecosystem.
  • KIP-83: Much welcome proposal that allows to instantiate clients with different security configurations in the same JVM. There are already patches available by Rajini Sivaram and Edurdo Comar and once integrated it will allow us to update MirrorMaker to support different security configurations on source and target clusters.
  • KIP-85: Allowing clients to take JAAS configurations dynamically rather than via a file. This will be huge for those of us implementing microservices in containers – adding files to containers has been very inconvenient.

In addition to ongoing Kafka improvements, there are other interesting news and blogs:

If you are interested in learning all about streaming data platforms, Confluent has released a 6-part online talk series focusing on Apache Kafka. You can view the recordings for the first two talks in the series by Jay Kreps and Jun Rao, and register for the upcoming sessions at www.confluent.io/apache-kafka-talk-series.

Subscribe to the Confluent Blog

S'abonner

More Articles Like This

Incremental Cooperative Rebalancing in Apache Kafka: Why Stop the World When You Can Change It?
Konstantine Karantasis

Incremental Cooperative Rebalancing in Apache Kafka: Why Stop the World When You Can Change It?

Konstantine Karantasis

There is a coming and a going / A parting and often no—meeting again. —Franz Kafka, 1897 Load balancing and scheduling are at the heart of every distributed system, and […]

Kafka Connect Improvements in Apache Kafka 2.3
Robin Moffatt

Kafka Connect Improvements in Apache Kafka 2.3

Robin Moffatt

With the release of Apache Kafka® 2.3 and Confluent Platform 5.3 came several substantial improvements to the already awesome Kafka Connect. Not sure what Kafka Connect is or need convincing […]

What’s New in Apache Kafka 2.3
Colin McCabe

What’s New in Apache Kafka 2.3

Colin McCabe

It’s official: Apache Kafka® 2.3 has been released! Here is a selection of some of the most interesting and important features we added in the new release. Core Kafka KIP-351 […]

Fully managed Apache Kafka as a Service!

Try Free