S3 Source connector nested fields #30827
Unanswered
helanto
asked this question in
Connector Questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello 👋
I am trying to create a source connector that uses JSONl files from S3. The JSONl have nested fields. I believe that the schema inference part does not infers schema that is deeply nested. The schema stays
{"type":"object"}
. There is also a relevant discussion in #23133.When tried to specify the schema on the connector creation manually, I get back an error. For example when I specify:
{"username": "string", "friends": "array", "information": {"type":"object", "properties":{"nested":"string"}}}
, I get back:The only way to workaround the issue is to update the schema in the connection details, using the update connection API. However this feels a bit hacky.
I wanted to ask what is the recommended approach to correctly specify nested schemas on S3 source connector ?
Do you consider existing behaviour as a bug or it's how it supposed to work ?
Deployment information
4.0.4
0.50.30
Beta Was this translation helpful? Give feedback.
All reactions