Hey Kafka fam,
What’s the correct way to set task-level overrides to producer settings in a
Kafka Connect task? For example, with MirrorMaker2, I’d expect the following
“producer.override.*” based configs to work based on the documentation, but in
in reality this does not change any of the produ
idate
the above information.
Hope this helps,
Greg
On Thu, Feb 13, 2025 at 9:35 AM Mehrtens, Mazrim
mailto:mmehr...@amazon.com.inva>lid> wrote:
> I’ve found that Kafka Connect never respects the
> “target.cluster.bootstrap.servers” configuration in the MirrorMaker2 task
> co
Does anyone know why MirrorMaker2 doesn’t replicate write ACLs?
This is the logic MM2 uses for choosing ACLs to replicate, which excludes GROUP
resources and ALLOW WRITE permissions:
https://github.com/apache/kafka/blob/trunk/connect/mirror/src/main/java/org/apache/kafka/connect/mirror/MirrorSou
I’ve found that Kafka Connect never respects the
“target.cluster.bootstrap.servers” configuration in the MirrorMaker2 task
config. It always uses the Kafka Connect broker information instead. Running
Kafka Connect on the source cluster causes an infinite loop of messages read
from the source cl
