Discover · getbruin.com

No picture published by getbruin.com

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.

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 this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

More like this

Also from getbruin.com

  1. Launching Bruin Cloud Streams: database CDC without KafkaKateryna Kozachenko getbruin.com
  2. How to enable Postgres logical replication for CDC (2026)Kateryna Kozachenko getbruin.com
  3. How to stop CDC from filling your Postgres disk with WALKateryna Kozachenko getbruin.com
  4. How to Get Automatic Data Lineage Across PipelinesKateryna Kozachenko getbruin.com
  5. How to Test Data Pipelines in CI/CDKateryna Kozachenko getbruin.com
  6. How to Enforce Data Contracts in a PipelineKateryna Kozachenko getbruin.com