Discard op code m change events #42431
Merged
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
1 task
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
area/connectors
rodireich
changed the title
rodireich
changed the title
octavia-squidington-iii
added
the
area/documentation
evantahler
approved these changes
Jul 23, 2024
...ces/src/main/kotlin/io/airbyte/cdk/integrations/debezium/internals/DebeziumRecordIterator.kt
Outdated
Show resolved
Hide resolved
…byte/cdk/integrations/debezium/internals/DebeziumRecordIterator.kt Co-authored-by: Evan Tahler <evan@airbyte.io>
|
/publish-java-cdk
|
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
Fixes #41647
Debezium change events are coming with an operation code.
Op code "m" signifies a "message" event that is irrelevant for syncing as it contains no before or after data.
In this case a 3rd party wrote arbitrary messages into the WAL log which caused us to fail parsing.
We want to only handle known event types.
How
Discard debezium change events that has
op: m.User Impact
Should not impact users as it should unblock cases a message event breaks us.
Can this PR be safely reverted and rolled back?