Airbyte MySQL composite-key snapshots: inspect the first key group
An exclusive first partition boundary can omit the minimum-key group even when synchronization succeeds.
A total count loses the location of the gap
Validate the first extraction boundary through inclusion of its key group as well as the total count. Truthound comparing only totals can reveal a shortage, but identifying the affected partition and keys requires a boundary contract. [1, 2, 3]
The missing minimum-prefix group
The public Airbyte MySQL report describes concurrent snapshots of a composite-primary-key table omitting rows sharing the minimum value of the first key column. It attributes the omission to an exclusive initial lower bound while the sync reports success. A successful single-column-key test cannot be generalized to this composite-key path. [1]
Count the boundary group independently
If a direct aggregate on the illustrative source snapshot establishes 100 rows in the minimum-prefix group, the extraction must retain 100 there. An extracted minimum-prefix group of 100 rows retains the approved boundary-group count. A group count of 0 means the first partition omitted the required scope. Growth in another group cannot compensate for a missing first group. [1, 3]
The grouped Truthound check
Record minimum keys and inclusion policy by partition, then compare the first group's actual count with its source reference. Keep composite-key controls separate from single-key success. Truthound Core's QueryGroupAggregateValidator can aggregate the prepared output by boundary group and verify that expected groups exist. Aligning source and output snapshots and correcting the connector's WHERE generation remain separate responsibilities. [1, 2, 3]
Application conditions
Obtain partition_id, lower_prefix_key and included_min_group_rows from the same source snapshot, linking the first-boundary inclusion policy to the output.
Alternatives
Prepare a snapshot control explicitly comparing inclusion at the first partition boundary.
Limitations
Truthound does not change the connector’s WHERE-boundary generator. Align source and extraction snapshots first.
Evidence
- Event checked
- Subject checked
- Modified
