[
https://issues.apache.org/jira/browse/KAFKA-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sönke Liebau resolved KAFKA-395.
--------------------------------
Resolution: Workaround
As this issue has not been touched in more than 6 years I think it is fairly
safe to assume that we can close this.
Any discussions around mirroring functionality are better addressed in the
MirrorMaker 2.0 KIP discussion.
Regarding the specifics of this issue, that can be worked around by placing
whitelists topics into a file and the paste-ing that file into the command as
shown below. I believe that this should be sufficient as a workaround.
{code:java}
// ./kafka-mirror-maker.sh --consumer.config ../config/consumer.properties
--producer.config ../config/producer.properties --whitelist "$(paste
whitelist.topics -d'|' -s)" --blacklist "$(paste blacklist.topics -d'|' -s)"
{code}
> kafka.tools.MirrorMaker black/white list improvement
> ----------------------------------------------------
>
> Key: KAFKA-395
> URL: https://issues.apache.org/jira/browse/KAFKA-395
> Project: Kafka
> Issue Type: Improvement
> Components: config
> Reporter: Dave DeMaagd
> Priority: Minor
>
> Current black/white list topics are specified directly on the command line,
> while functional, this has two drawbacks:
> 1) Changes become unwieldy if there are a large number of running instances -
> potentially many instances to restart, which can have implications for data
> stream lag
> 2) Maintaining the list itself can become increasingly complex if there are a
> large number of elements in the list (particularly if they are complex
> expressions)
> Suggest extending the way that black/white lists can be fed to the mirror
> maker application, in particular, being able to specify the black/white list
> as a file (or possibly a generic URI). Thinking that this could be
> accomplished either by adding '--whitelistfile' and '--blacklistfile' command
> line parameters, or modifying the existing '--blacklist' and '--whitelist'
> parameters to include a 'is this a valid file?' test and decide how to handle
> it based on that (if it is a file, read it, if not, use current behavior).
> Follow up suggestion would be to have the mirror maker process check for
> updates to the list file, and on change, validate and reload it, and run from
> that point with the new list information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
