Hello-
We are having an issue with generating a dynamic metadata structure using "select * from [table] limit 1" (Using Postgres) however one of the columns is of ARRAY type and cannot be mapped. Is there a way to tell the graph to default unknown datatypes to string? We are trying to avoid creating a separate table that only houses the structure of a file as this structure is 99% the same as the table we are writing to.
We are having an issue with generating a dynamic metadata structure using "select * from [table] limit 1" (Using Postgres) however one of the columns is of ARRAY type and cannot be mapped. Is there a way to tell the graph to default unknown datatypes to string? We are trying to avoid creating a separate table that only houses the structure of a file as this structure is 99% the same as the table we are writing to.
-
Hello jblythe99,
unfortunately, ARRAY type fields are currently not supported in the dynamic metadata generating process. However, this issue is currently being discussed within our development team so I will let you know as soon as the decision is agreed upon. As for any potential workaround, I would suggest either specifying column names in the query used in the dynamic metadata definition or creating a view on the table in Postgres which does not include the ARRAY type column (then using the query as is). However, I bear in mind that both approaches ultimately defeat the purpose of dynamic metadata definition.
Regards,
Please sign in to leave a comment.
Comments 3