getPartitionKey falls back to the table name when the configured routing_key column is missing from the event, and swallows any error on the way (src/processor/processor.zig:171-188). A typo in routing_key (or the default id on a table without an id column) is never reported: every message gets the same key and lands in one partition, killing ordering-by-key and partition balance without a trace in the logs.
Ask: validate at startup that the routing key column exists on the configured table (next to the other table checks in the validator), and log a warning on the runtime fallback path.
getPartitionKeyfalls back to the table name when the configuredrouting_keycolumn is missing from the event, and swallows any error on the way (src/processor/processor.zig:171-188). A typo inrouting_key(or the defaultidon a table without anidcolumn) is never reported: every message gets the same key and lands in one partition, killing ordering-by-key and partition balance without a trace in the logs.Ask: validate at startup that the routing key column exists on the configured table (next to the other table checks in the validator), and log a warning on the runtime fallback path.