kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "huxi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-4351) Topic regex behavioral change with MirrorMaker new consumer
Date Fri, 28 Oct 2016 06:12:58 GMT

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

huxi resolved KAFKA-4351.
    Resolution: Resolved

> Topic regex behavioral change with MirrorMaker new consumer
> -----------------------------------------------------------
>                 Key: KAFKA-4351
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4351
>             Project: Kafka
>          Issue Type: Bug
>          Components: tools
>    Affects Versions:
>            Reporter: Dustin Cote
>            Assignee: huxi
>            Priority: Minor
> There is a behavioral change when you use MirrorMaker with the new consumer versus the
old consumer with respect to regex parsing of the input topic list.  If one combines a regex
with a comma separated list for the topic list with old consumer implementation of MirrorMaker,
it works ok.  Example:
> {code}
> --whitelist '.+(my|mine),topic,anothertopic'
> {code}
> If you pass this in with the new consumer implementation, no topics are found.  The workaround
is to use something like:
> {code}
> --whitelist '.+(my|mine)|topic|anothertopic'
> {code}
> We should make an effort to be consistent between the two implementations as it's a bit
surprising when migrating. I've verified the problem exists on but I don't see at
first any fix to the problem in later versions.

This message was sent by Atlassian JIRA

View raw message