You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Confirming issue, same case - field with variable number of keys of same type with schema like below: "Header": { "type": "object", "additionalProperties": { "type": "array", "items": { "type": "string" } } },
is not working as expected, I'm converting to Avro with s3 sink connector and resulting avro schema part is:
{ "name": "Header", "type": { "name": "properties.Header", "type": "record", "fields": [] } },
"additionalProperties" are not affecting anything
Reopening #12 since was never fully resolved and I am having similar issues.
As a toy example, I have an event in which one of fields is an object with ever-changing fields. For example:
I will never know what the keys of
changingField
will be, but i know that they will be of boolean type.So, i create a schema:
I then have a JDBC sink connector that I would define as following:
However, this will create an error:
Since the
changingField
has not been given a valid Struct.Any help on how I can use the connector for this use-case?
Thanks!
The text was updated successfully, but these errors were encountered: