-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
<Your answer>
What is the connector configuration?
<Your answer>
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
<Your answer>
What behaviour do you expect?
<Your answer>
What behaviour do you see?
<Your answer>
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
<Your answer>
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
<Your answer>
How to reproduce the issue using our tutorial deployment?
<Your answer>
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
It will allow to speed up incremental snapshots for tables that have composite PK. See DBZ-5071 for more details.
Implementation ideas (optional)
By allowing the ORDER BY column to be configurable, users might not default to PK of the table for incremental snapshots, but instead provide a column that is unique.
- impacts account
-
DBZ-5071 Use row value constructors to speed up multi-column queries for incremental snapshots
- Closed
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release