Let's make SQL great again - Google BigQuery's Pipe query syntax
summary
BigQuery adds a suffix-based pipe query syntax (|>) that makes queries read top‑to‑bottom: start with from, then sequential operators like where, aggregate, join, each stage emitting a valid intermediate query. Existing SQL remains valid and the planner rewrites pipes into the same relational algebra, so performance holds. Table‑valued functions already wire into the pipeline; planned additions include assert/log/describe for breakpoint‑style debugging. The result collapses multi‑level subqueries and turns thousands‑line nests into composable steps.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:25SQL's clause order problems
- 14:35Why evolve SQL
- 17:51BigQuery's pipe syntax
- 21:49Pipe syntax operators
- 23:56Standard vs pipe syntax
- 26:04Live demo
- 37:07Pipe syntax advantages
- 37:47Future use cases
- 43:06Try pipe syntax
- 44:11Call to action
related talks
12mIntroducing Steampipe - select * from cloud
50mServerless SQL Pipelines
32mUnlearning SQL
45mMore Than a Query Language: SQL in the 21st Century
41mBreakout Session
32mBecause SQL is everywhere but you don't want to use it
39mMore Than a Query Language: SQL in the 21st Century
49mScylla, Charybdis, and the mystery of Quill