🐛 Source Chargebee: add missing incremental dependency
to full-refresh
sub-streams with Incremental
parent streams
#46343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Resolving:
Story:
incremental dependency
for CDK5.8.0
, for cases when substream isfull-refresh
and the parent stream isincremental
causing the source to read all of the parent records first and then yield them to substream, which itself causes theheartbeat issues
for the Platform.How
incremental_dependency: true
to the next streams:contact
attached_item_stream
quote_line_group_stream
User Impact
No impact is expected, for the existing Customers.
Can this PR be safely reverted and rolled back?