Hello, We are puzzled trying to figure out how schema compatibility strategy for a topic gets evaluated. We want to have

ALWAYS_COMPATIBLE

across our whole cluster, but some topics resolve as

FULL

. We are not 100% sure, but this problem seems to be with newer topics or with specific namespaces. Are we missing some layer, configuration, or some other policy that influences how the strategy type gets resolved? Here are two topics and how they resolve differently:

# pulsar-admin brokers get-runtime-config | grep schemaCompatibilityStrategy
schemaCompatibilityStrategy    ALWAYS_COMPATIBLE


# pulsar-admin namespaces get-schema-compatibility-strategy platform/activation
UNDEFINED

# pulsar-admin topicPolicies get-schema-compatibility-strategy <persistent://platform/activation/activation-target-changed>
null

# pulsar-admin topicPolicies get-schema-compatibility-strategy --applied <persistent://platform/activation/activation-target-changed>
FULL


# pulsar-admin namespaces get-schema-compatibility-strategy platform/controller
UNDEFINED

# pulsar-admin topicPolicies get-schema-compatibility-strategy <persistent://platform/controller/modem-scan-update-message-generated>
null

# pulsar-admin topicPolicies get-schema-compatibility-strategy --applied <persistent://platform/controller/modem-scan-update-message-generated>
ALWAYS_COMPATIBLE