Summary
User is unable to find the Postgres connector source in Airbyte, even though it was previously available. User is considering upgrading the connector to the latest version and is concerned about potential impact on existing pipelines.
Question
Hi team,
Urgent help needed for this basic bug. I am not able to find Postgres connector source as showing in screenshot attached. Earlier it was there, even I have a pipeline running with this source already.
Do I need to upgrade the source, as it is showing installed is 2.0.32 and latest is version 3.3.26. If I upgrade it directly from UI, will it cause any problem to existing pipelines?
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
["missing-postgres-connector-source", "upgrade-connector", "existing-pipelines", "version-3.3.26"]
You have a typo, you should type “postgres” not “postges”
Sorry for the typo, but that’s not the problem:
What happens if you click “Show hidden results”?
It was not appearing even after that.
But I updated the source to latest version and it is showing up now in sources. Thanks!
But as you are from Airbyte team, can you help me with Amazon ads source also:
I Have added all required fields like client id, secret, token. But still getting the following error:
'No profiles found after filtering by Profile ID and Marketplace ID'```
I’m facing the same issue both on airbyte OSS and Cloud with the same error
'No profiles found after filtering by Profile ID and Marketplace ID'```
I made sure that I was able to call Amazon Ads API myself with the Client ID / Secret / Refresh token
I even tried to fill Profile Ids and Marketplace Ids but nothing seems to be solving the issue
Hello I haven’t used Amazon ads, but for info the code is here: https://github.com/airbytehq/airbyte/tree/master/airbyte-integrations/connectors/source-amazon-ads/source_amazon_ads The code doesn’t seems huge, maybe you could try debug there
Hello!
Thanks for the link, I found the issue for me. The account I was trying to link is an “agency” account and is filtered out https://github.com/airbytehq/airbyte/blob/806974ce7638c7f0e8184d307490a382926819e0/airbyte-integrations/connectors/source-amazon-ads/source_amazon_ads/streams/profiles.py#L23|here
So apparently the amazon ads connector does not support amazon DSP API calls.
Someone tried to add a <Issues · airbytehq/airbyte · GitHub Amazon DSP connector> but it has not been approved (apparently because the connector development was in python)
I might try to create a low-code connector for Amazon DSP in the next few weeks
Hey, thanks for pointing it out!
But I am not using it for an agency account, I am trying it as an advertiser self only.
Not sure, why I am still getting the issue.
Ok then I would suggest to try yourself debugging using the framework <airbyte/airbyte-integrations/connectors/source-amazon-ads at 806974ce7638c7f0e8184d307490a382926819e0 · airbytehq/airbyte · GitHub here >
It’s how I found the issue, maybe you can try changing some parameters and see if something works for you
Are you using airbyte cloud or OSS ?
> So apparently the amazon ads connector does not support amazon DSP API calls.
> Someone tried to add a <Issues · airbytehq/airbyte · GitHub Amazon DSP connector> but it has not been approved (apparently because the connector development was in python)
Small update on this, I tried to do it with the low-code connector but apparently the asynchronous nature of the API makes not possible to implement with only low-code
https://airbytehq.slack.com/archives/C027KKE4BCZ/p1708834384893759?thread_ts=1708801986.007599&cid=C027KKE4BCZ
I’m going to take a look at the PR and try to update it
Hi,
So I tried debugging it locally, the issue I found is in this line:
https://github.com/airbytehq/airbyte/blob/806974ce7638c7f0e8184d307490a382926819e0/airbyte-integrations/connectors/source-amazon-ads/source_amazon_ads/streams/profiles.py#L23C17-L23C60|https://github.com/airbytehq/airbyte/blob/806974ce7638c7f0e8184d307490a382926819e0[…]nectors/source-amazon-ads/source_amazon_ads/streams/profiles.py
Here it is applying profile filter on seller and vendor.
But in the Amazon ads documentation (https://advertising.amazon.com/API/docs/en-us/reference/2/profiles#tag/Profiles/operation/listProfiles) it is mentioned that it performs inclusive AND operation on the types.
But as my ad account is having only view access and type also only seller, I am not getting any profiles in the check itself and it was failing with “message”: “‘No profiles found after filtering by Profile ID and Marketplace ID’”
So question is, can I not use the Airbyte Amazon-ads connector with only view access and only “seller” type?
I am having this same issue, I have seller and view only and providing my Profile ID which i get with my secret/token and it keeps saying ‘No profiles with seller or vendor type found after filtering by Profile ID’