Announcing MCP Toolbox Java SDK v1.0: Agentic data access for the enterprise
cloud.google.com·6d ago
Cloud & Infrastructure
The New Stack·Sep 6·5 min read
Polars 2.0 pre-release comes with a 5x speed boost — but it could change row order
TL;DR
Polars 2.0 pre-release introduces a streaming engine that boosts query performance by up to 5x, but it may alter the order of returned rows.
✦ Why It Matters
Test your existing Polars queries with the new version to ensure row order consistency.
Key Takeaways
- Test your existing code for row order dependencies.
- Use maintain_order=True to enforce row order when necessary.
- Consider switching back to the in-memory engine if needed.
- Explore the new API features for improved data parsing.
How It Works
The streaming engine processes LazyFrame queries in batches, allowing for better memory management and faster execution. This method enables users to work with datasets that exceed available memory.
⚠ The Catch
The streaming engine does not guarantee row order for operations like join and group_by, which may lead to unexpected results in data pipelines.