supabase / etl / 35300635733

79%

Build Type

push

github

Committed by web-flow

Commit Message

clickhouse: handle primary-key updates and event ordering (#966)

* ClickHouse handles primary key changes

* MergeTree preserves transaction order

* ClickHouse handles key update edge cases

* ClickHouse key update rules are explicit

* MergeTree tests share one event row

* MergeTree ordering tests have clear phases

* Reject ClickHouse metadata column collisions

* Prioritize ClickHouse replica identity errors

* ref(clickhouse): name primary key width helper

* ref(clickhouse): distinguish source and destination rows

* style(clickhouse): space validation branches

* docs(clickhouse): clarify key equality semantics

* test(clickhouse): cover reordered composite keys

* test(etl): use LSN handoff barrier

* Remove ClickHouse legacy migration

* Make ClickHouse table upgrades explicit

* Test ClickHouse split-write replay recovery

* Cover Postgres primary-key update edge cases

* Address ClickHouse upgrade review feedback

* Structure PR tests with scenario comments

* Dedupe ClickHouse float key equality helpers

Factor the copy-pasted F32/F64 scalar and array NaN-equality arms of
postgres_key_cell_equal into generic helpers over a small PostgresFloat
trait. No behavior change.

* Cover non-key update in ClickHouse update spine

The spine test was repurposed into a primary-key-changing update,
leaving the most common case (non-key update) without direct
integration coverage. Use two rows so one plain value update and one
key change are asserted independently on both engines.

* Align update test scenario comment style

* Reject legacy MergeTree layout on schema change

A live Relation event for a closed-alpha MergeTree table (no
cdc_tx_ordinal) ran its ALTER and recorded the metadata as Applied,
so the operator only saw the upgrade error on the next DML write.
The recovery path already rejected this layout before any DDL.

Check the current endpoint against the actual columns in
handle_relation_event before the cache clear, Applying write, and
DD... (continued)

Coverage Stats

480 of 497 new or added lines in 3 files covered. (96.58%)

17 existing lines in 4 files now uncovered.

58627 of 74803 relevant lines covered (78.38%)

7855.07 hits per line