The problem I have with no wildcard or regex support in whitelist/blacklist is the following (I'm fine with not having the ability to specify both whitelist and blacklist at the same time):
Let's say I've producers in DC1 writing to topic A and the ones in DC2 writing to topic B. I can have a mirroring setup for this specific scenario. Now, let's say we have a whole set of new producers who want to write to topic C in DC1. This will require us to manually change the whitelist configuration in the mirroring setup. Whereas, if we had wild card support we could have done something like the following: Have all producers in DC1 write to topic names prefixed with "dc1:" and all producers in DC2 write to topics with "dc2:" prefix. If whitelist/blacklist supports wildcards we could have just specified something like "dc1:*" for whitelist and then not worry about producers creating new topics as long as they stick to the naming convention. On Thu, Jul 26, 2012 at 9:58 AM, Jun Rao <jun...@gmail.com> wrote: > Currently, you can't specify both whitelist/blacklist in an embedded > consumer, but you can specify one of them. Is that not enough for you? And > you can always run multiple instances of mirror maker, if necessary. > > Thanks, > > Jun > > >
