[
https://issues.apache.org/jira/browse/KAFKA-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-103:
-----------------------------
Attachment: kafka-103-incremental-v2.patch
Note that this is an incremental patch.
That is a good point - i.e., we have told clients that we are changing the old
whitelist config to mirror.topics.whitelist. If they simply do a rename then
nothing is going to get mirrored, so I agree that backward-compatibility is
important.
btw, I think a better fix (that would also help KAFKA-104) is to disallow
invalid topics, but it would be better to think about that more carefully.
> Make whitelist/blacklist mirror configs more consistent
> -------------------------------------------------------
>
> Key: KAFKA-103
> URL: https://issues.apache.org/jira/browse/KAFKA-103
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.7
> Reporter: Joel Koshy
> Priority: Minor
> Attachments: kafka-103-incremental-v2.patch, kafka-103-patch.v1
>
>
> The blacklist config for kafka mirrors is a comma separated list of topics.
> However, the whitelist config is a comma-separated list of
> "topics:numthreads" pairs, which allows for a multi-threaded consumer in the
> mirror. It will be good to keep the two configs consistent in format. So, we
> can make the whitelist config a comma-separated list of topics and provide a
> config (say, kafka.mirror.consumer.threads) that will specify the number of
> threads to use for all topics in the whitelist (if present).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
