DBZ-7351 Avoid child data snapshots from PostgreSQL parent tables #5159
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
|
Welcome as a new contributor to Debezium, @koleo. Reviewers, please add missing author name(s) and alias name(s) to the COPYRIGHT.txt and Aliases.txt respectively. |
When PostgreSQL tables are configured with inheritance (INHERIT clause), data is streamed by Debezium from the table where the data resides (usually the child tables). However, during the initial/incremental snapshot, Debezium selects all data from the parent tables, including child data, which pushes unexpected/duplicate data into the topics (all data from child tables). Using a "SELECT ... FROM ONLY" retrieves only data from the current table and avoids retrieving data from child tables. Signed-off-by: Nicolas Payart <npayart@gmail.com>
|
@koleo Please try to run |
|
Yes I will 👌 |
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.
When PostgreSQL tables are configured with inheritance (INHERIT clause), data is streamed by Debezium from the table where the data resides (usually the child tables).
However, during the initial/incremental snapshot, Debezium selects all data from the parent tables, including child data, which pushes unexpected/duplicate data into the topics (all data from child tables).
Using a "SELECT ... FROM ONLY" retrieves only data from the current table and avoids retrieving data from child tables.