kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5276) Support derived and prefixed configs in DescribeConfigs (KIP-133)
Date Sat, 23 Sep 2017 04:49:07 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Guozhang Wang updated KAFKA-5276:

*Reminder to the contributor / reviewer of the PR*: please note that the code deadline for
1.0.0 is less than 2 weeks away (Oct. 4th). Please re-evaluate your JIRA and see if it still
makes sense to be merged into 1.0.0 or it could be pushed out to 1.1.0, or be closed directly
if the JIRA itself is not valid any more, or re-assign yourself as contributor / committer
if you are no longer working on the JIRA.

> Support derived and prefixed configs in DescribeConfigs (KIP-133)
> -----------------------------------------------------------------
>                 Key: KAFKA-5276
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5276
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>             Fix For: 1.0.0
> The broker supports config overrides per listener. The way we do that is by prefixing
the configs with the listener name. These configs are not defined by ConfigDef and they don't
appear in `values()`. They do appear in `originals()`. We should change the code so that we
return these configs. Because these configs are read-only, nothing needs to be done for AlterConfigs.
> With regards to derived configs, an example is advertised.listeners, which falls back
to listeners. This is currently done outside AbstractConfig. We should look into including
these into AbstractConfig so that the fallback happens for the returned configs.

This message was sent by Atlassian JIRA

View raw message