@vladyslav_zavalykhatko and @michael_harris - There’s an issue open on pipelinewise-tap-postgres related to

sdc_recursive_string_array

https://github.com/transferwise/pipelinewise-tap-postgres/issues/94

Posting current (non-elegant) workaround here incase anyone is interested

Best idea I have for a workaround is to just avoid that table entirely in the select and use another method for EL (such as extract from source, load to storage bucket in flat file format to force an unnest of arrays, then load from storage bucket to warehouse)

Another option would be to override the schema definition in catalog, for instance to use the simpler

{"type": ["null", "array"], "items": {"type": "string"}}

in place of

{"type": ["null", "array"], "items": {"$ref": "#/definitions/sdc_recursive_string_array"}}

. In theory, overriding the schema should remove this ref - assuming the postgres tap uses it as provided.

@aaronsteers yeah, I know this issue - I opened it 😄