Module dataflow::render::debezium [−][src]
Structs
Track whether or not we should skip a specific debezium message
Helper to track information for logging on deduplication
If we need to deal with debezium possibly going back after it hasn’t seen things. During normal (non-snapshot) operation, we deduplicate based on binlog position: (pos, row), for MySQL. During the initial snapshot, (pos, row) values are all the same, but primary keys are unique and thus we can get deduplicate based on those.
When to start and end full-range tracking