liveBook · Manning

Runtime filtering

As explained in Architecting an Apache Iceberg Lakehouse

A query-execution technique that derives runtime filter values from one part of a query and applies them to reduce data scanned elsewhere.

Runtime filtering reduces data movement in federated query execution by deriving relevant values from one side of a join and applying them to the larger dataset before retrieval. This lowers the data scanned, transmitted, and processed, improving latency and resource use. section 8.3.4

Runtime filtering is most valuable when:

  • A small table identifies a limited set of values needed from a much larger remote table. section 8.3.4
  • Federated queries would otherwise transfer substantial data across remote systems or network infrastructure. section 8.3.4
  • A semantic layer supplies relationship and join logic that helps locate effective filter points. section 8.3.4

Filtering a large joined dataset

A federated query first identifies relevant values from a small table, then applies those values while retrieving the larger joined dataset, avoiding unnecessary scans and transfers. section 8.3.4

How Architecting an Apache Iceberg Lakehouse covers it

How deep it goes
Explains value derivation, early filter application, and semantic-layer support, but does not specify implementation internals.
Examples
Uses small-table and large-table joins across federated sources as the primary performance example.
What it assumes
Assumes familiarity with SQL joins, query execution, and federated data sources.
What you can do after
Apply runtime filtering to reduce scans, transfers, latency, and resource use in federated joins.
How it connects
Connects federated queries with joins, semantic layers, external query pushdown, and dynamic filtering.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting an Apache Iceberg Lakehouse. The section links point to the parts of the book it draws on.