You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2025/02/27 22:41:00 UTC
[jira] [Resolved] (KAFKA-18860) Clarify the KRaft missing feature
[ https://issues.apache.org/jira/browse/KAFKA-18860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai resolved KAFKA-18860.
------------------------------------
Resolution: Fixed
trunk: [https://github.com/apache/kafka/commit/e2d9ced098c35068900746afe608820ae967d5a7]
4.0: https://github.com/chia7712/kafka/commit/e7a13f759ee3509f108b146aa7d3c9c6d3161255
> Clarify the KRaft missing feature
> ---------------------------------
>
> Key: KAFKA-18860
> URL: https://issues.apache.org/jira/browse/KAFKA-18860
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Luke Chen
> Assignee: TengYao Chi
> Priority: Major
> Fix For: 4.0.0
>
>
> In the KRaft [missing feature|https://kafka.apache.org/documentation/#kraft_missing] section, there's one remaining:
>
> Modifying certain dynamic configurations on the standalone KRaft controller
>
> We should clarify what it means and make it clear to users. To me, I don't think there's anything we can't update to KRaft controller. But not 100% sure what the original author mean.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)