<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/R0YGj36hu" -->

---
title: Polars 2.0 release candidate: streaming engine becomes...
description: Polars 2.0 release candidate (installable via pip install polars==2.0rc1) makes the streaming engine the default for all LazyFrame collect() calls, delivering...
canonical: https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Polars 2.0 release candidate: streaming engine becomes the default, with a few gotchas | daily.dev
og:description: Polars 2.0 release candidate (installable via pip install polars==2.0rc1) makes the streaming engine the default for all LazyFrame collect() calls, delivering...
og:url: https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu
og:image: https://api.daily.dev/og/posts/R0YGj36hu.png
og:image:alt: Polars 2.0 release candidate: streaming engine becomes the default, with a few gotchas
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Polars 2.0 release candidate: streaming engine becomes the default, with a few gotchas

**[Collections](https://daily.dev/sources/collections)** · 2 min read · 7 upvotes · 1 comments

## Summary

Polars 2.0 release candidate (installable via pip install polars==2.0rc1) makes the streaming engine the default for all LazyFrame collect() calls, delivering roughly 5x faster execution and lower memory usage on large datasets. The catch: the streaming engine no longer guarantees row order for join, group_by, and unpivot operations, which can silently break pipelines that implicitly relied on ordering. Fixes include explicit sorting, maintain_order=True, or reverting to the in-memory engine. The release also tightens defaults — lossy is_in coercions, mismatched-length concatenation, and ambiguous casts now raise errors instead of silently corrupting data — and removed APIs like melt and join_nulls now raise descriptive errors pointing to replacements. A migration guide is available, with a faster S3 reader and cost-based query planner planned for the 2.x series.

## Content

Polars 2.0 has a release candidate out now (`pip install polars==2.0rc1`), and the headline change is that the streaming engine is now the default for all LazyFrame `collect()` calls. For most users that means roughly 5x faster query execution and meaningfully lower memory usage on large datasets — which is a real improvement worth getting excited about.

That said, there's a catch worth knowing before you upgrade.

## Row order is no longer guaranteed

The streaming engine doesn't preserve row order for operations like `join`, `group_by`, and `unpivot`. If your pipeline depends on incidental row ordering — and plenty do, even when you don't realize it — things can break silently.

The fix is straightforward: sort explicitly where order matters, or pass `maintain_order=True` to the relevant operations. If you need the old behavior across the board, you can revert to the in-memory engine via the engine affinity setting.

## Stricter defaults throughout

The major version bump also comes with stricter behavior in a few areas that previously let bad data slide:

- Lossy type coercions in `is_in` now raise errors instead of silently producing wrong results
- Mismatched-length horizontal concatenation now raises an error
- Ambiguous casts raise errors — you'll need to use explicit methods like `.str.to_date()` instead

These are good changes. Silent data corruption is worse than a loud error.

## Removed APIs surface helpful errors

APIs that were removed — like `melt` and `join_nulls` — now raise `AttributeRemovedError` or `ArgumentRemovedError` with pointers to their replacements, rather than just crashing with a confusing message. That's a nice touch for migration.

A full migration guide is available on the Polars site. The 2.x series also has more coming: a faster S3 reader and a cost-based query planner are both planned.

## Questions this post answers

### Does Polars 2.0 guarantee row order after group_by or join operations?

No. In Polars 2.0 release candidate, the streaming engine is the new default for LazyFrame collect() calls, and it does not preserve row order for operations like join, group_by, and unpivot. To keep the old ordering behavior, pass maintain_order=True to the relevant operations or switch back to the in-memory engine via the engine affinity setting.

_daily.dev helps data engineers track breaking changes like this before an upgrade causes silent bugs._

### What breaking changes does upgrading to Polars 2.0 introduce?

Polars 2.0 makes the streaming engine default, which can silently reorder rows in join, group_by, and unpivot unless explicitly handled. It also tightens error handling: lossy type coercions in is_in, mismatched-length horizontal concatenation, and ambiguous casts now raise errors instead of silently producing wrong results, and removed APIs like melt and join_nulls raise descriptive errors pointing to their replacements.

_Teams planning a Polars upgrade can follow migration gotchas like these through daily.dev._

### How much faster is the Polars streaming engine compared to the previous default execution engine?

The streaming engine, now default in the Polars 2.0 release candidate, delivers roughly 5x faster query execution along with meaningfully lower memory usage on large datasets compared to the prior in-memory default.

_Developers evaluating Polars performance gains can keep tabs on releases like this via daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@trevorsuna** · 0 upvotes

> Making streaming the default is a big win, but row order is exactly the kind of implicit contract that slips past unit tests. Before 2.0 I’d add explicit sorts at API and output boundaries and compare representative LazyFrames under both engines; stricter coercion errors are painful once, while silent data shifts linger.

## Similar posts on daily.dev

- [Release of Polars 2.0](https://daily.dev/posts/release-of-polars-2-0-84cwf427y) · Polars Blog · 4 upvotes · 0 comments
- [Announcing Polars 2.1](https://daily.dev/posts/announcing-polars-2-1-wq74kbq6p) · Polars Blog · 1 upvotes · 0 comments
- [Polars 2.0 vs pandas vs DuckDB: 2 GB CSV, 4 GB Memory Limit](https://daily.dev/posts/polars-2-0-vs-pandas-vs-duckdb-2-gb-csv-4-gb-memory-limit-va0ij7pou) · Medium · 0 upvotes · 0 comments
- [Polars 2.0 vs DuckDB 2.0](https://daily.dev/posts/polars-2-0-vs-duckdb-2-0-tqkatjwjj) · Confessions of a Data Guy · 0 upvotes · 0 comments

---

Tags: [#python](https://daily.dev/tags/python), [#data-engineering](https://daily.dev/tags/data-engineering), [#polars](https://daily.dev/tags/polars)

[View this post on daily.dev](https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Polars 2.0 release candidate: streaming engine becomes the default, with a few gotchas","url":"https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu"},"datePublished":"2026-09-06T16:58:19.250Z","dateModified":"2026-09-13T19:34:14.543Z","description":"Polars 2.0 release candidate (installable via pip install polars==2.0rc1) makes the streaming engine the default for all LazyFrame collect() calls, delivering...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/57605212c27dafd97eb7ea8440819f44?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/57605212c27dafd97eb7ea8440819f44?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"python,data-engineering,polars","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Polars 2.0 release candidate: streaming engine becomes the default, with a few gotchas"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu","comment":[{"@type":"Comment","text":"Making streaming the default is a big win, but row order is exactly the kind of implicit contract that slips past unit tests. Before 2.0 I’d add explicit sorts at API and output boundaries and compare representative LazyFrames under both engines; stricter coercion errors are painful once, while silent data shifts linger.","datePublished":"2026-09-13T13:52:42.782Z","url":"https://daily.dev/posts/R0YGj36hu#c-B6LCtplaf","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/polars-2-0-release-candidate-streaming-engine-becomes-the-default-with-a-few-gotchas-r0ygj36hu#faq","mainEntity":[{"@type":"Question","name":"Does Polars 2.0 guarantee row order after group_by or join operations?","acceptedAnswer":{"@type":"Answer","text":"No. In Polars 2.0 release candidate, the streaming engine is the new default for LazyFrame collect() calls, and it does not preserve row order for operations like join, group_by, and unpivot. To keep the old ordering behavior, pass maintain_order=True to the relevant operations or switch back to the in-memory engine via the engine affinity setting. daily.dev helps data engineers track breaking changes like this before an upgrade causes silent bugs."}},{"@type":"Question","name":"What breaking changes does upgrading to Polars 2.0 introduce?","acceptedAnswer":{"@type":"Answer","text":"Polars 2.0 makes the streaming engine default, which can silently reorder rows in join, group_by, and unpivot unless explicitly handled. It also tightens error handling: lossy type coercions in is_in, mismatched-length horizontal concatenation, and ambiguous casts now raise errors instead of silently producing wrong results, and removed APIs like melt and join_nulls raise descriptive errors pointing to their replacements. Teams planning a Polars upgrade can follow migration gotchas like these through daily.dev."}},{"@type":"Question","name":"How much faster is the Polars streaming engine compared to the previous default execution engine?","acceptedAnswer":{"@type":"Answer","text":"The streaming engine, now default in the Polars 2.0 release candidate, delivers roughly 5x faster query execution along with meaningfully lower memory usage on large datasets compared to the prior in-memory default. Developers evaluating Polars performance gains can keep tabs on releases like this via daily.dev."}}]}
```

