Technology

Polars releases version 2.0 release candidate with default streaming engine

The major update alters default behaviors to improve performance while requiring explicit parameters for preserved row order.

Updated Sep 3, 2026 · 08:18 UTC1 reports

The short version

The Polars development team released the first release candidate for Polars 2.0, with a final release expected in the coming weeks.
LazyFrame queries will now default to the streaming engine, which developers estimate will run roughly five times faster in aggregate and reduce memory usage.
The streaming default removes guaranteed row ordering for operations like joins and group-bys unless explicitly configured by users.
Developers must adapt to stricter type handling, new exception types for deprecated parameters, and API adjustments.

The Polars team launched the first release candidate, version 2.0rc1, ahead of a planned full 2.0 release in the following weeks.[Hacker News]
LazyFrame queries will default to the streaming engine, which the maintainers estimate will be roughly five times faster in aggregate and significantly decrease memory usage.[Hacker News]
Operations such as joins, group_by, and unpivot no longer guarantee preserved row order under the default streaming engine unless users specify maintain_order=True or set the engine affinity to in-memory.[Hacker News]
Polars 2.0 introduces stricter rules, including length checks during horizontal concatenation instead of silent null-filling and preventing silent lossy type conversions.[Hacker News]
The release introduces dedicated typed exceptions, AttributeRemovedError and ArgumentRemovedError, to guide users toward updated syntax for removed functionality.[Hacker News]

The exact release date for the final, non-candidate Polars 2.0 version has not been formally specified beyond a window of the following weeks.[Hacker News]