Summary
User reports a bug in Connector Builder where multi-column primary keys are being converted from an array to a string separated by ‘.’ after a recent update, affecting functionality even after republishing the connector.
Question
Hello Airbyte team,
I’ve noticed that since couple days ago something changed in Connector Builder, where there any recent releases? What happens that all the streams with multi-column primary key get broken, seems that after update what was previously array, became string separated by . symbol (see screenshot). This happens even if I republish connector with no changes, only older saved versions of connector works. Any idea how to fix this?
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
['connector-builder', 'multi-column-primary-key', 'bug', 'recent-releases']
If the problem persists in a published connector, this then signals to me that it’s the CDK regression, not just a Builder issue.
Can you take a look at what version: key works for you in the previous version of the connector?
Are you using Airbyte Cloud, or OSS? If OSS, what version?
Further investigation shows that version: 5.14.0 was still working, but since update to version 6.1.0. Btw we are talking about Airbyte Cloud version
We’ll look into this and resolve this soon. Regressions in Builder happen, especially in paths less traveled (multi-column PKs are something that we don’t really support very well), I’d expect a couple days turnaround give or take
<@U07UW9ZTXQW> thank you for the details!
so the release must have been in period after 2024-10-23. Is there any way to force older version? Simply editing YAML file for connector seems to not work since version is automatically overwritten after Publish action?
Nope, Builder will build connector on publish with latest available CDK (major CDK version management should be better, true).
<@U07UW9ZTXQW>, would it be OK for you to post / DM me a link to your workspace, to this specific project in Connector Builder, and would it be OK for our engineers to hit test reads with your credentials? That way we can validate things work when we work on a fix, and debug what exactly is crapping out.
yes, sure feel free to do that 
https://github.com/airbytehq/airbyte/pull/48394 the fix is in this PR — we’ll get this reviewed and merged, then we’d have to patch up the Builder to bump the CDK version it uses, but overall we’re on good track.
Nope, haven’t noticed these, though I’m kind of stuck with older version of connector and just simply waiting for this to be resolved, so haven’t experimented much.
<@U07UW9ZTXQW> this issue should now be resolved, so you can go into the Builder, publish a new version, and refresh your source schema in your connection to fix the primary key
Hey <@U02T7NVJ6A3> thanks for letting me know. Already tested it out, seems to be working perfectly now
That’s great, thank you for reporting the issue!
If the problem persists in a published connector, this then signals to me that it’s the CDK regression, not just a Builder issue.
Can you take a look at what version: key works for you in the previous version of the connector?
Are you using Airbyte Cloud, or OSS? If OSS, what version?
Further investigation shows that version: 5.14.0 was still working, but since update to version 6.1.0. Btw we are talking about Airbyte Cloud version
We’ll look into this and resolve this soon. Regressions in Builder happen, especially in paths less traveled (multi-column PKs are something that we don’t really support very well), I’d expect a couple days turnaround give or take
<@U07UW9ZTXQW> thank you for the details!
so the release must have been in period after 2024-10-23. Is there any way to force older version? Simply editing YAML file for connector seems to not work since version is automatically overwritten after Publish action?
Nope, Builder will build connector on publish with latest available CDK (major CDK version management should be better, true).
<@U07UW9ZTXQW>, would it be OK for you to post / DM me a link to your workspace, to this specific project in Connector Builder, and would it be OK for our engineers to hit test reads with your credentials? That way we can validate things work when we work on a fix, and debug what exactly is crapping out.
yes, sure feel free to do that