I posted this in community, but I really should ha...
# connector-contributions
w
I posted this in community, but I really should have posted this over here in contributions: https://airbytehq.slack.com/archives/C021JANJ6TY/p1727393649448859?thread_ts=1727301133.789399&cid=C021JANJ6TY > I've put up a PR for a proposed fix for Issue 45345: 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 🙂 Sharing here in the hope that the community or devs can help take this the rest of the way. (
u
You’re right! Let me take a look
w
I'm also happy to post of video of some of the insideousness I saw with the latest version of destination PG having two streams drop data into the same underlying table if needed (esp if the fix belongs deeper in the CDK, which would be beyond my ability and time to sink into it 🙂 )