You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 26
Next »
Release Dates
- KIP Freeze: Sep 30, 2020 (a KIP must be accepted by this date in order to be considered for this release)
- Feature Freeze: Oct 7, 2020 (major features merged & working on stabilization, minor features have PR, release branch cut; anything not in this state will be automatically moved to the next release in JIRA)
- Code Freeze: Oct 21, 2020
- Release: estimated Nov 6, 2020
These dates are goals and subject to change, but we expect to stay on the Time Based Release Plan unless unexpected critical issues come up. While the target release date is fixed at ~2w after code freeze, RCs will roll out as needed until the release vote passes.
The release manager is Bill Bejeck
How to Contribute
Before code freeze:
- Participate in votes and discussions to land or postpone the open KIPs.
- Review patches. We anticipate that this release will be bottlenecked mostly on reviews. The more reviewers, the more content we can fit in.
- Write unit/integration/system tests. We want to preserve the tradition of high-quality releases in Apache Kafka.
After code freeze:
- Write more unit/integration/system tests. We want to preserve the tradition of high-quality releases in Apache Kafka.
- Improve documentation
- Test the release candidates
- Open blocker JIRAs on critical issues found. Open non-blocker JIRAs on any other issues found.
- Fix critical bugs
- Review bug fixes
- Vote on RCs. Even though only PMC votes are binding, community votes are super important as we evaluate the readiness of the release
Open Issues
| key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Also feel free to refer to this release page for more details of the included tickets.
Planned KIP Content
Note: The planned content is not binding - final content will be based the features committed by branch-cutting date. See Kafka Improvement Proposals for the full list of KIPs.
| KIP | JIRA | Component |
|---|
| KIP-671: Introduce Kafka Streams Specific Uncaught Exception Handler |
Unable to render Jira issues macro, execution error.
,
Unable to render Jira issues macro, execution error.
, | Kafka Streams |
| KIP-662: Throw Exception when Source Topics of a Streams App are Deleted |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-654: Aborted transaction with non-flushed data should throw a non-fatal exception |
Unable to render Jira issues macro, execution error.
| Kafka Clients |
| KIP-651 - Support PEM format for SSL certificates and private key |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-648: Renaming getter method for Interactive Queries |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-632: Add DirectoryConfigProvider |
Unable to render Jira issues macro, execution error.
,
Unable to render Jira issues macro, execution error.
|
|
| KIP-626: Rename StreamsConfig config variable name |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-620 Deprecate ConsumerConfig#addDeserializerToConfig and ProducerConfig#addSerializerToConfig |
Unable to render Jira issues macro, execution error.
| Kafka Clients |
| KIP-617: Allow Kafka Streams State Stores to be iterated backwards |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-616: Rename implicit Serdes instances in kafka-streams-scala |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-613: Add end-to-end latency metrics to Streams |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-612: Ability to Limit Connection Creation Rate on Brokers |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-607: Add Metrics to Kafka Streams to Report Properties of RocksDB |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-601: Configurable socket connection timeout in NetworkClient |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-599: Throttle Create Topic, Create Partition and Delete Topic Operations |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-597: MirrorMaker2 internal topics Formatters |
Unable to render Jira issues macro, execution error.
|
|
| KIP-588: Allow producers to recover gracefully from transaction timeouts |
Unable to render Jira issues macro, execution error.
| Kafka Clients |
| KIP-584: Versioning scheme for features |
Unable to render Jira issues macro, execution error.
|
|
| KIP-572: Improve timeouts and retries in Kafka Streams |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-554: Add Broker-side SCRAM Config API |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-545: support automated consumer offset sync across clusters in MM 2.0 |
Unable to render Jira issues macro, execution error.
| Mirror Maker 2.0 |
| KIP-497: Add inter-broker API to alter ISR |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-478 - Strongly typed Processor API |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-450: Sliding Window Aggregations in the DSL |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-431: Support of printing additional ConsumerRecord fields in DefaultMessageFormatter |
Unable to render Jira issues macro, execution error.
| Kafka Tools |
| KIP-216: IQ should throw different exceptions for different errors |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-81: Bound Fetch memory usage in the consumer |
Unable to render Jira issues macro, execution error.
| Kafka Clients |
Postponed to subsequent release
| KIP | JIRA | Component |
|---|
| KIP-653: Upgrade log4j to log4j2 |
Unable to render Jira issues macro, execution error.
|
|
| KIP-623: Add "internal-topics" option to streams application reset tool |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-608 - Expose Kafka Metrics in Authorizer |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-590: Redirect Zookeeper Mutation Protocols to The Controller |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-589 Add API to update Replica state in Controller |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-580: Exponential Backoff for Kafka Clients |
Unable to render Jira issues macro, execution error.
| Kafka Clients |
| KIP-508: Make Suppression State Queriable |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-466: Add support for List<T> serialization and deserialization |
Unable to render Jira issues macro, execution error.
|
|
| KIP-418: A method-chaining way to branch KStream |
Unable to render Jira issues macro, execution error.
| Kafka Streams |
| KIP-373: Allow users to create delegation tokens for other users |
Unable to render Jira issues macro, execution error.
|
|
| KIP-359: Verify leader epoch in produce requests |
Unable to render Jira issues macro, execution error.
| Core |
| KIP-280: Enhanced log compaction |
Unable to render Jira issues macro, execution error.
| Core |
|
|
|