liveBook · Manning

Continuous query

A continuous query remains active and incrementally emits updated results as new data arrives.

How 2 Manning books explain it

Kafka Streams in Action, Second Edition

A push query is a continuous ksqlDB query that emits changing results to the client that issued it without persisting those results in a topic.

How it is used
Streams ongoing asynchronous query results directly to the requesting client.
How deep it goes
Defines execution and delivery behavior, then demonstrates SELECT, WHERE, and LIMIT without detailing query internals.
Examples
Uses activity_leaders selections with EMIT CHANGES, a total_steps filter, and a ten-row limit.
What you can do after
Apply it via ksqlDB to receive filtered, continually changing stream or table results in a client.

Read how Kafka Streams in Action, Second Edition explains continuous query →

Kafka for Architects

A continuous query is a query that remains active and incrementally updates its results as new data arrives.

How it is used
Processes incoming Kafka events continuously to deliver low-latency filtered or aggregated results to downstream consumers.
How deep it goes
Explains stream filtering, grouping, and windows, and sketches translation into Kafka Streams applications without low-level implementation details.
Examples
Uses expensive-order filtering, per-country counts, and one-hour tumbling-window counts.
What you can do after
Build it with ksqlDB by defining a stream, applying SQL transformations, and emitting results to an output topic.

Read how Kafka for Architects explains continuous query →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.