Summary
JSON Schema with additionalProperties set to true is not respected by the S3 destination connector, leading to unexpected results in the parquet file.
Question
Has anyone ever had an issue with "additionalProperties": true not being respected when it’s in the JSON Schema? I have that as the schema of one of my connectors, but the S3 destination connector does not seem to respect it. Here’s what the parquet file ends up looking like:
I created a ticket https://github.com/airbytehq/airbyte/issues/36326|here, but curious to know if anyone in the community has seen this before.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.