Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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

[connector-builder] Substream Only Fetches Records from the First Page of Parent Stream #40734

Open
avirajsingh7 opened this issue Jul 4, 2024 · 8 comments · May be fixed by #40671
Open

[connector-builder] Substream Only Fetches Records from the First Page of Parent Stream #40734

avirajsingh7 opened this issue Jul 4, 2024 · 8 comments · May be fixed by #40671

Comments

@avirajsingh7
Copy link
Contributor

Topic

Connector-Builder-Ui

Relevant information

We're encountering an issue with source connectors configured through the UI where substreams are only making API calls to records fetched from the first page of their parent streams. This means that even if the parent stream has a significant number of records (e.g., 23k in this case), the substream will only process parent_id from first_page record of parent_stream (e.g., 546 records).

I have verified the records on DB and last record of substream is from last record of parent stream fetched from first api call.

Here's manifest.yaml file, I have configured this to get record for each api_call in substream(For debugging purpose).

@marcosmarxm marcosmarxm changed the title Substream Only Fetches Records from the First Page of Parent Stream [connector-builder] Substream Only Fetches Records from the First Page of Parent Stream Jul 4, 2024
@marcosmarxm
Copy link
Member

@airbytehq/dev-marketplace-contributions can someone take a look in this issue?

@Stockotaco
Copy link

I have the same issue. My substream runs for every item in the parent stream but only the first page of the parent stream.

@natikgadzhi
Copy link
Contributor

Mentioned on Community Slack: https://airbytehq-team.slack.com/archives/C021JANJ6TY/p1720192514494299

We're looking, but no ETA yet.

@natikgadzhi
Copy link
Contributor

@Stockotaco @avirajsingh7 I have a hunch — does it matter if the substream OR the parent stream are full refresh or incremental? If incremental is possible and you switch to incremental, does the problem go away?

@Stockotaco
Copy link

In my case both parent and sub-streams are full refresh syncs, not incremental.

Incremental won't work in my case.

@avirajsingh7
Copy link
Contributor Author

avirajsingh7 commented Jul 6, 2024

@natikgadzhi both are full refresh, #40573 is also a same issue, looks like bug

@natikgadzhi
Copy link
Contributor

Oh, I think we have a fix for this here: #40671

@natikgadzhi
Copy link
Contributor

@ChristoGrab, can you please test Builder locally with CDK with this patch applied, and confirm this works for Builder as well? If yes, also review and approve @brianjlai's pull request, and let's make sure to ship it on Monday.

@natikgadzhi natikgadzhi assigned ChristoGrab and unassigned brianjlai Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment