supabase / etl / 42177715185

81%

Build Type

push

github

Committed by web-flow

Commit Message

feat(apply): report relations that mismatch schema (#1212)

A RELATION message is matched to the stored schema by column names
only, but tuples are decoded by position. A stale snapshot whose names
were swapped by renames, or whose column type changed without a DDL
message, is accepted. Values can then land in the wrong columns, or be
decoded with the old type. This happens on partition leaves published
without publish_via_partition_root, whose parent ALTERs emit no leaf
DDL message.

Detect where the materialized decoder stops matching the relation's
column order and types, then log it and count it in
etl_relation_schema_mismatches_total by mismatch_kind: column_count,
name_order, text_compatible_type, or type. Types are compared after the
OID mapping used for stored schemas, so domains, enums, and other types
decoded as text agree. Replication continues with the stored schema,
as before, so the rate is known before mismatches stop pipelines.

The relation agreement properties and minimal counterexamples that were
ignored as known defects now run and assert detection.

Refs PIPE-1283.

Coverage Stats

77 of 102 new or added lines in 3 files covered. (75.49%)

23 existing lines in 5 files now uncovered.

62586 of 77373 relevant lines covered (80.89%)

44638.74 hits per line