Proposed fix for conflicting relations and truncation in Destination Postgres

Summary

This message discusses a proposed fix for conflicting relations and truncation in the Destination Postgres connector. The user has submitted a PR and is seeking help with unit tests and a debate on whether the fix should be at the CDK or connector level.


Question

I’ve put up a PR for a proposed fix for <Issues · airbytehq/airbyte · GitHub 45345>: <https://github.com/airbytehq/airbyte/pull/45941|PR 45941 - Destination Postgres - Fix Conflicting relations and truncation causing streams to write raw streams to same table>

I’ve tried to document the PR, the approach, and a debate that I think could be had if the actual fix for this should be deeper in the CDK vs at the connector level. I am also still working on getting all the unit tests passing, but I’m not a Java/Kotlin expert, and certainly not when the class hierarchy jumps from Koitlin to Java and Back to Kotlin :slightly_smiling_face: Sharing here in the hope that the community or devs can help take this the rest of the way.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["proposed-fix", "conflicting-relations", "truncation", "destination-postgres", "PR", "unit-tests", "CDK", "java", "kotlin"]