Styxis
Company
Knowledge

RisingWave CDC name collisions: verify live routing separately from backfill

A topic name normalized from special characters may not uniquely identify its original source table.

When a display name becomes a routing key

Check collisions before treating a normalized name as a unique entity identity. Truthound's allowed-pair check can verify source-table-to-destination relationships. Keeping only the normalized name makes it difficult to recover evidence that different tables were merged. [1, 2, 3]

Live events follow a different path

The public RisingWave shared-CDC reproduction describes Debezium replacing special characters with underscores, allowing tables such as orders$ and orders_ to share a routing key. Backfill reads the original table directly and can succeed while live changes are mixed or missed. Initial-load success does not establish the provenance of continuing changes. [1]

Inspect the complete source inventory

Check the full mapping from source-table identities to actual routing keys. After backfill, test that live inserts and updates reach only their intended tables. Restricting registered names may not prevent contamination if the shared source still reads other upstream tables. Inspect the complete collection scope. [1, 3]

An illustrative misrouting condition

In an illustrative approved mapping, the number of source tables sent to another destination must be 0. A count of 0 source tables sent to a wrong destination satisfies this mapping condition. A count of 1 identifies a table whose live events reached an unapproved destination. Derive expected destinations from original table identities and approved configuration, not by reinterpreting received topic names. Preserve source identity even when different tables use the same primary-key value. [1, 3]

Routing correction beyond Truthound

Truthound Core's ColumnPairInSetValidator can inspect approved source-table–destination pairs. It does not replace the CDC router. Select a supported path that preserves source identity, then retest live changes as well as initial backfill. A single naming restriction is not evidence that every upstream collision is prevented. [1, 2, 3]

Application conditions

Link source_table_id, sanitized_topic and registered_destination across the complete collection scope to the independently approved mapping, checking actual live delivery.

Alternatives

Investigate supported routing that preserves original table identity instead of relying on normalized names.

Limitations

  • Name restrictions alone do not necessarily prevent contamination from other upstream tables already being read. Truthound does not replace the CDC router.

Evidence

Event checked
Subject checked
Modified