[
https://issues.apache.org/jira/browse/KAFKA-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911044#comment-17911044
]
TengYao Chi commented on KAFKA-18450:
-------------------------------------
I think the second approach is better since it's more straightforward for users
to find out which properties are for which component.
Furthermore, we could also leverage throwing exceptions or other programmatical
ways to inform users what's wrong.
> display which role can use the config
> -------------------------------------
>
> Key: KAFKA-18450
> URL: https://issues.apache.org/jira/browse/KAFKA-18450
> Project: Kafka
> Issue Type: Improvement
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Major
>
> After migrating zk to kraft, we identified several configurations that are no
> longer used by brokers. These include create.topic.policy.class.name,
> alter.config.policy.class.name, delegation.token.expiry.check.interval.ms,
> delegation.token.expiry.time.ms, etc. While these configurations are now
> exclusive to the controller, determining the exact scope for each
> configuration remains a challenge to users.
> While users can technically add all configurations to both controller and
> broker properties, our documentation should clearly indicate the intended
> scope of each configuration. This will not only enhance user understanding
> but also guide them in correctly configuring the broker and controller.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
