[hotfix] remove kafka compatibility from the roadmap#2027
Merged
wuchong merged 1 commit intoapache:mainapache/fluss:mainfrom Nov 26, 2025
polyzos:rm-kafka-compatibilitypolyzos/fluss:rm-kafka-compatibilityCopy head branch name to clipboard
Merged
[hotfix] remove kafka compatibility from the roadmap#2027wuchong merged 1 commit intoapache:mainapache/fluss:mainfrom polyzos:rm-kafka-compatibilitypolyzos/fluss:rm-kafka-compatibilityCopy head branch name to clipboard
wuchong merged 1 commit intoapache:mainapache/fluss:mainfrom
polyzos:rm-kafka-compatibilitypolyzos/fluss:rm-kafka-compatibilityCopy head branch name to clipboard
Conversation
wuchong
approved these changes
Nov 26, 2025
2 tasks
Ugbot
pushed a commit
to Ugbot/fluss
that referenced
this pull request
Apr 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removing the Kafka compatibility from the roadmap, as it might be confusing to users. As we discussed on our community sync Kafka compatibility is always welcomed as part of contributions, however it won't be on our direct plans because we want Fluss to set the way beyond Kafka. Moreover:
Providing a kafka-compatible api means using Fluss as a drop-in replacement for Kafka. Fluss provides way much functionality though, so users won't see benefits, by just using the kafka api.
After discussions with people supporting the kafka-api, seems like its lot of work, and the result is not the best one.. So we will have to put too much effort and then there is also lots of maintenance effort.