feat(source-bing-ads): migrate accounts stream to manifest#59136
feat(source-bing-ads): migrate accounts stream to manifest#59136Aldo Gonzalez (aldogonzalez8) merged 33 commits intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| output, _ = self.read_stream(self.stream_name, SyncMode.full_refresh, self._config, "app_install_ad_labels_empty") | ||
| assert len(output.records) == 0 | ||
| assert len(output.logs) == 11 | ||
| assert len(output.logs) == 12 |
There was a problem hiding this comment.
The ConcurrentDeclarativeSource in read() calls self. _ group_streams (), which calls self.streams()
At the end of that, it calls super.read(), which is AbstractSource.read(), which collects streams again.
The override of the streams method in source-bing-ads creates an authentication client, so we initialize it twice, and we receive an extra log entry for "Fetching access token ...".
There was a problem hiding this comment.
Should we just remove this? It does not seem to indicate any behavior for this connector and is going to be flaky if we add logs in the CDK
Can we check in the history is there is a reason it was added?
There was a problem hiding this comment.
I removed it but added support to check the behavior, meaning I assert the expected logs for the test behavior.
| ) | ||
|
|
||
|
|
||
| def build_request_2(config: Dict[str, Any]) -> HttpRequest: |
There was a problem hiding this comment.
I assume this is temporary until we migrate all to REST, right? Can we add a document why this is different? I guess this is just the order or stuff
There was a problem hiding this comment.
Yes, I have documented this.
Maxime Carbonneau-Leclerc (maxi297)
left a comment
There was a problem hiding this comment.
-
Can we remove the user stream here?
-
Do we have difference between REST and SOAP for account stream?
| ) as service_call_mock: | ||
| catalog = CatalogBuilder().with_stream(stream_name, sync_mode).build() | ||
| return read(SourceBingAds(), config, catalog, state, expecting_exception), service_call_mock | ||
| # return read(SourceBingAds(), config, catalog, state, expecting_exception), service_call_mock |
There was a problem hiding this comment.
nit: to remove
There was a problem hiding this comment.
Copy-paste is the source of all evil, removed.
|
|
||
| class RequestBuilder: | ||
| def __init__(self, resource: str = None) -> None: | ||
| self._spreadsheet_id = None |
There was a problem hiding this comment.
nit: clean this
There was a problem hiding this comment.
Copy-paste is the source of all evil, removed.
| output, _ = self.read_stream(self.stream_name, SyncMode.full_refresh, self._config, "app_install_ad_labels_empty") | ||
| assert len(output.records) == 0 | ||
| assert len(output.logs) == 11 | ||
| assert len(output.logs) == 12 |
There was a problem hiding this comment.
Should we just remove this? It does not seem to indicate any behavior for this connector and is going to be flaky if we add logs in the CDK
Can we check in the history is there is a reason it was added?
|
Ok, interpretation of these regressions_tests results:
Follo up: find a connection with TaxInformation |
Sadly, I couldn't find any connection with TaxInformation filled to compare, so I think I'm okay with letting it be as it is, making the RC, and seeing if we get any feedback from this change. What I did was create a test for the LinkedAgencies transformation we just added. I ran another Progressive Rollout for a connection with four accounts and got similar results to exposed above.
I expect to create the RC tomorrow and follow up. |
What
Fix the unit and integration tests to pass as the base source was changed to
YamlDeclarativeSourceDepends on: airbytehq/airbyte-python-cdk#519
Resolves: https://github.com/airbytehq/airbyte-internal-issues/issues/12668
How
User helper for source creation.
Review guide
User Impact
A step further to migrate to low code.
Can this PR be safely reverted and rolled back?