history eventhub is configured with --cleanup-policy Delete instead of Compact.

[jeacott1]

The sample history hub configured is configured as follows.

echo "deploying schema history event hub"
az eventhubs eventhub create \
    --resource-group $RESOURCE_GROUP \
    --namespace-name $EVENTHUB_NAMESPACE \
    --name $EVENTHUB_SCHEMA_HISTORY \
    --partition-count 1 \
    --cleanup-policy Delete \
    --retention-time-in-hours 168 \
    --output none

This seems like terrible advice for any production environment.
Shouldn't it be cleanup-policy compact and infinite retention?

however, when I set this I cannot get debezium to write to the topic/hub without CORRUPT_MESSAGE errors. Works fine when --cleanup-policy Delete