NULL Keys Silently Break BigQuery Joins and MERGEs
getbruin.com
This is what was read here when it was published. Sabri Karagonen no longer carries it in what it publishes now.
Listen to this summary
A NULL in a join key never matches itself, so your incremental MERGE quietly duplicates rows and your joins quietly drop them. Here is why it happens, why the obvious null-safe fix (IS NOT DISTINCT FROM) turns your join into a cross join, and the OR-form that stays a hash join, with a full BigQuery benchmark.
More ways to use this
Open on another device
Scan to open this page. Your saved notes and account access are not included.
Fix Tenable One findings where developers work: Tenable and OpenAI Daybreak Defense Factory