Or perhaps we could provide a more general ReplicationPolicy that renames
according to a pattern string, and the Legacy and Prefixless use-cases
could just use that.
On Mon, Mar 16, 2020 at 12:32 PM Andrew Otto wrote:
> +1 to this general idea. If Wikimedia ever gets around to switching to
> MM
+1 to this general idea. If Wikimedia ever gets around to switching to
MM2, we'll need something like this as our apps manually do the topic
prefixing for active <-> active replication.
Perhaps 'Legacy' isn't a good name for this type of replication? There may
be more uses cases like Marcin's wh
Marcin, I just created this jira per your suggestion:
https://issues.apache.org/jira/browse/KAFKA-9726
I've assigned it to myself but I'm happy to give it up.
Ryanne
On Mon, Mar 16, 2020 at 2:37 AM Marcin Wieloch
wrote:
> Hello Ryanne,
>
> Thank you for these clarifications. I am glad that the
Hello Ryanne,
Thank you for these clarifications. I am glad that the use case of “prefixless”
replication is in-line with your vision for further development of
MirrorMaker2; I forgot indeed that already KIP-382 mentioned that
LegacyReplicationPolicy.
I have not found however any JIRA issue a
Hello Marcin, actually KIP-382 includes LegacyReplicationPolicy (not yet
released) which is similar to your PrefixlessReplicationPolicy and the
MigrationReplicationPolicy mentioned. I don't think these are hacky, though
maybe the documentation could better address what to do when a method
doesn't n
