We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue was raised to us on Discourse.
For example, the Snowplow site_search schema has a field like this:
"filters": { "type": "object", "additionalProperties": { "type": [ "string", "boolean" ] } },
...it would yield two different columns called "filters" in the ddl:
"filters" VARCHAR(1024) ENCODE ZSTD, "filters" VARCHAR(4096) ENCODE ZSTD,
This only happens if additionalProperties is an object, not a boolean.
additionalProperties
This might be related to #104 but it's not exactly the same, so I'm making it a different issue.
The text was updated successfully, but these errors were encountered:
Redshift: Fix schemas with additionalProperties object getting duplic…
a704cfa
…ate columns (close #134)
9e7dddd
Duplicate of #55
Sorry, something went wrong.
4ba3204
c068ad6
…ate columns (close #134) (cherry picked from commit 4ba3204)
No branches or pull requests
This issue was raised to us on Discourse.
For example, the Snowplow site_search schema has a field like this:
...it would yield two different columns called "filters" in the ddl:
This only happens if
additionalProperties
is an object, not a boolean.This might be related to #104 but it's not exactly the same, so I'm making it a different issue.
The text was updated successfully, but these errors were encountered: