There is currently no logic based on the enum state CollationMatchesDefault::kNoDefault. It looks like the state was added in anticipation for future use. The CollationMatchesDefault enum is only used in time-series code and the CollationMatchesDefault::kNoDefault is supposed to be used for collection-less aggregation. We should just get rid of this state in order to simplify the logic around collators.