Snowplow users commonly use schemas with no nested fields. Previously, we were creating a string column and loading the string field {}. But there is no benefit to loading this redundant data.
By omitting a column for these schemas, it means we support schema evolution if the user ever adds a nested field to the empty schema.
For empty schemas with additionalProperties: true we retain the old behaviour of loading the original JSON as a string.
Snowplow users commonly use schemas with no nested fields. Previously, we were creating a string column and loading the string field
{}. But there is no benefit to loading this redundant data.By omitting a column for these schemas, it means we support schema evolution if the user ever adds a nested field to the empty schema.
For empty schemas with
additionalProperties: truewe retain the old behaviour of loading the original JSON as a string.