🐛 Source PayPal Transactions: update manifest.yaml to use the latest CDK version to fix the STATE for Incremental streams
#37435
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…ransactions/update-manifest-to-the-latest-version
octavia-squidington-iii
added
the
area/documentation
1 task
maxi297
approved these changes
Apr 19, 2024
It's updated, take a look here: https://github.com/airbytehq/airbyte/pull/37435/files#diff-f3f66141f908f43848cb00a86d54a85976e83802173bdbc8cfb3b77b625aa014 |
bazarnov
deleted the
baz/source/paypal-transactions/update-manifest-to-the-latest-version
branch
strosek
pushed a commit
that referenced
this pull request
Apr 24, 2024
…t CDK version to fix the STATE for Incremental streams (#37435)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: #37385
Having the old manifest version caused to use of the
slice_endvalue instead of themost recent record observed, switching to the latest version of the CDK and manifest version - fixes the issue.How
0.50.2to0.80.0formanifest.yamlUser Impact
Users that have experienced missing records, because the STATE value was far from the actual data value - should reset those streams and re-sync the data once again.
Can this PR be safely reverted and rolled back?