Hi team, we are running a standalone MAE Consumer. However, we realise that to produce entity change events to platform event topic, we have to set

MCL_CONSUMER_ENABLED

to

true

in GMS instead of setting it in MAE Consumer (which alr has

MAE_CONSUMER_ENABLED="true"

). And the entity change events are produced by GMS instead of MAE Consumer. This doesn’t look aligned with the code I understand. From the code,

MetadataChangeLogProcessor

is enabled when either MAE_CONSUMER_ENABLED or MCL_CONSUMER_ENABLED is true - thus, this ChangeLog processor is alr enabled in MAE Consumer. As

EntityChangeEventGeneratorHook

is one of the hooks invoked by

MetadataChangeLogProcessor

. My understanding is that the entity change events should be produced by the standalone MAE Consumer (instead of GMS) without additional config of

MCL_CONSUMER_ENABLED

on GMS. Do I miss some gap here? 🙇 (running with DataHub v0.8.35, deployed with Helm chart 0.2.72)

I met the same situation like you, could you please tell me how to fix this?

we’ve been running non-standalone mode since then