Hi everyone, I see that it's possible to <configur...
# all-things-deployment
b
Hi everyone, I see that it's possible to configure consumer group ids for datahub-mce-consumer and datahub-mae-consumer. how can it be done for the following consumer groups? 1. generic-platform-event-job-client 2. datahub-usage-event-consumer-job-client
1
looks like someone else is also experiencing this issue. https://github.com/acryldata/datahub-helm/issues/319
Following env vars work. • METADATA_CHANGE_EVENT_KAFKA_CONSUMER_GROUP_ID • METADATA_CHANGE_LOG_KAFKA_CONSUMER_GROUP_ID • METADATA_CHANGE_PROPOSAL_KAFKA_CONSUMER_GROUP_ID • PLATFORM_EVENT_KAFKA_CONSUMER_GROUP_ID • DATAHUB_USAGE_EVENT_KAFKA_CONSUMER_GROUP_ID • DATAHUB_UPGRADE_HISTORY_KAFKA_CONSUMER_GROUP_ID
r
@broad-battery-31188 how are these environment variables linked to the appropriate consumer groups 1. mce-consumer-job-client 2. generic-mce-consumer-job-client 3. generic-mae-consumer-job-client 4. datahub-usage-event-consumer-job-client 5. generic-platform-event-job-client 6. datahub-duhe-consumer-job-client-gms Can you provide a 1 to 1 mapping for these default consumer group ids with their corresponding environment variables?
never mind figured out the mapping
Copy code
DATAHUB_USAGE_EVENT_KAFKA_CONSUMER_GROUP_ID -> datahub-usage-event-consumer-job-client
METADATA_CHANGE_EVENT_KAFKA_CONSUMER_GROUP_ID -> mce-consumer-job-client
METADATA_CHANGE_LOG_KAFKA_CONSUMER_GROUP_ID -> generic-mae-consumer-job-client
METADATA_CHANGE_PROPOSAL_KAFKA_CONSUMER_GROUP_ID -> generic-mce-consumer-job-client
PLATFORM_EVENT_KAFKA_CONSUMER_GROUP_ID -> generic-platform-event-job-client
DATAHUB_UPGRADE_HISTORY_KAFKA_CONSUMER_GROUP_ID -> datahub-duhe-consumer-job-client-gms
plus1 1