-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Zendesk Support: Unpin CDK #36403
Merged
Merged
Zendesk Support: Unpin CDK #36403
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 ↗︎
|
…ytehq/airbyte into christo/zendesk-support-cdk
brianjlai
approved these changes
Mar 29, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm and I agree with your assessment. Thanks for meticulously researching this and for the follow up ticket. great work!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/connectors
Connector related issues
area/documentation
Improvements or additions to documentation
connectors/source/zendesk-support
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
test_sequential_read
test.Note: Incremental Substream Bug 🐛🚨
I encountered a bug in the connector that I believe is due to incremental substreams using the same logic for handling stream state as top-level incremental streams (ie, a single cursor value as opposed to per-partition keys). This logic can lead to records being dropped during incremental syncs, as is the case with one of the expected records for the
article_comment_votes
stream. This stream has two records in our sandbox. Comparing the two existingarticle_comment_votes
timestamps:{"updated_at": "2023-06-22T00:33:42Z"} -> This record gets read and updates state
{"updated_at": "2023-06-22T00:33:40Z"} -> This record is skipped despite having never been read
Although this is the only stream that threw an expected_records failure, all incremental substreams use this same logic, and as such are affected. However, given that:
I think the best plan of action is to ship the CDK update, and allow the fix to be included in the upcoming migration. I've created an issue to track this for visibility.