Skip to content

Tracking issue for the new streaming engine #20947

Description

@coastalwhite

From 1.31.1, Polars has a new streaming engine. In time, it will become the default engine, as it is usually faster and uses less memory. All queries that run on the in-memory engine should run on the streaming engine (please file a bug otherwise), but certain operations might not have a native streaming implementation yet (in which case they will transparently fall back to the in-memory engine).

This issue tracks the progress of adding functionality natively to the streaming engine.

The streaming engine can be used by using LazyFrame.collect(engine='streaming') or LazyFrame.sink_*(...). The physical plan can be visualized as a dot graph by using .show_graph(engine='streaming', plan_stage='physical').

Sources

Sinks

Out-of-core

Streaming Nodes

Aggregates

Plan translation to streaming

Datatypes

  • Everything

Other

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-streamingRelated to the streaming engine

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions