Kia ora, I had a quick search in the mailing list archive to see if this had come up previously, apologies if it's already been covered and I missed it.
A user in the Confluent Slack hit an error with a composite type (which is effectively a dynamic type in PG, IIRC? I never encountered them in Postgres until today) which yielded the following error message: > org.postgresql.util.PSQLException: ERROR: column "orchestration_details" is of type orchestration_obj_type but expression is of type character varying > Hint: You will need to rewrite or cast the expression Given that they're types that only exist in a particular DB, and there's no (AFAICT) super-type that KC could infer them to be, I was thinking that a potential solution might be to expose to users the ability to configure other types that need casting in like these existing ones? https://github.com/confluentinc/kafka-connect-jdbc/blob/master/src/main/java/io/confluent/connect/jdbc/dialect/PostgreSqlDatabaseDialect.java#L86 If this might be a viable approach, I'd like to contribute it, but it's been a while since I've submitted a PR, would this require a KIP beforehand? (Or am I even asking in the right place, given the JDBC sink is controlled by Confluent? I'm unsure of the overlap these days) Ngā mihi, Liam Clarke-Hutchinson
