Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Ads Connector says it supports multiple customer ids but only accepts one. #2903

Closed
cgardens opened this issue Apr 15, 2021 · 8 comments · Fixed by #3154
Closed

Google Ads Connector says it supports multiple customer ids but only accepts one. #2903

cgardens opened this issue Apr 15, 2021 · 8 comments · Fixed by #3154
Assignees
Labels
area/connectors Connector related issues type/bug Something isn't working

Comments

@cgardens
Copy link
Contributor

Expected Behavior

  • Google Ads allows taking in multiple customer ids at once.
  • Google Ads connector allows taking multiple customer ids at once

Current Behavior

  • Google Ads connector says it allows multiple customer ids at once
  • Google Ads connector does not allow taking multiple customer ids at once

Steps to Reproduce

Screenshot 2021-04-15 at 15 50 13

Airbyte Version

0.19.0-alpha

Connector Version (if applicable)

Adwords: 0.2.1

@cgardens cgardens added the type/bug Something isn't working label Apr 15, 2021
@cgardens cgardens added this to the Connectors April 16th, 2021 milestone Apr 15, 2021
@cgardens
Copy link
Contributor Author

@sherifnada fyi

@jamakase
Copy link
Contributor

jamakase commented Apr 15, 2021

Isn't it better to handle such case as array of strings as we already have component for this?

@cgardens
Copy link
Contributor Author

yes. i agree artem. that sounds like the better approach.

@sherifnada sherifnada added the area/connectors Connector related issues label Apr 17, 2021
@sherifnada sherifnada removed this from the Connectors April 16th, 2021 milestone Apr 18, 2021
@sherifnada
Copy link
Contributor

agreed that this should be a string list. I'm not sure there is a way of changing this type without breaking backwards compatibility.

should be a simple fix to change the spec pattern from ^[0-9]{10}$ to ^[0-9]{10}(,[0-9]{10})*$

@michel-tricot
Copy link
Contributor

I think we should break backward compatibility here. We will need a strategy to handle that in the future.

@keu
Copy link
Contributor

keu commented Apr 30, 2021

@sherifnada so what will be the fix? are we going for a list or string?

@po3na4skld
Copy link
Contributor

@sherifnada so what will be the fix? are we going for a list or string?

As I understood, UI supports list so we will use it and not a string

@po3na4skld
Copy link
Contributor

po3na4skld commented May 20, 2021

During integration testing I got one test failed. Test is failing due to the fact that the stream is actually empty when trying to do testIncrementalSyncWithState. The name of the stream: KEYWORDS_PERFORMANCE_REPORT

The problem is also described in this issue: #2929

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants