OpenSearch Dashboards
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
Comparison · Analytics
Polars vs Citus
A side-by-side editorial comparison of Polars and Citus — release velocity, themes, recent moves, and the top alternatives to consider.
Polars vs Citus: at a glance
What is Polars?
The streaming engine is stable and the API is being narrowed — Polars is clearing ground for a breaking release
Polars publishes two trains into one feed: Python releases roughly weekly through 1.42.0 to 1.43.2, and Rust releases on their own numbering, with 0.54.4 carrying the milestone that the streaming engine is stabilized. The dominant thread across the Python releases is deprecation — casts from string to temporal types, numeric-to-categorical and categorical-to-integer casts, casts from non-nested dtypes into lists, bitwise ops between integers and booleans, cat.get_categories(), cat.to_local(), LazyFrame.profile(), and to_struct() calls without field names. Alongside it, cloud IO keeps getting attention: bytes-based concurrency control, callback sinks on cloud, and non-blocking path expansion.
What is Citus?
Citus keeps three Postgres branches alive while chasing each new major
Citus publishes synchronized maintenance releases across at least three live branches — 14.1, 13.3 and 12.1.13 all went out on the same day in July 2026 — with contents that are almost entirely backports of the same handful of upstream fixes. The substantive release in the window is Citus 14.0 from February, which added PostgreSQL 18.1 support. Release titles are inconsistent, several carrying release dates that contradict their publication date.
Polars vs Citus: editorial side-by-side
Polars
5.0ANALYTICS
The streaming engine is stable and the API is being narrowed — Polars is clearing ground for a breaking release
◆ Current state
Polars publishes two trains into one feed: Python releases roughly weekly through 1.42.0 to 1.43.2, and Rust releases on their own numbering, with 0.54.4 carrying the milestone that the streaming engine is stabilized. The dominant thread across the Python releases is deprecation — casts from string to temporal types, numeric-to-categorical and categorical-to-integer casts, casts from non-nested dtypes into lists, bitwise ops between integers and booleans, cat.get_categories(), cat.to_local(), LazyFrame.profile(), and to_struct() calls without field names. Alongside it, cloud IO keeps getting attention: bytes-based concurrency control, callback sinks on cloud, and non-blocking path expansion.
◆ Where it's heading
A deprecation batch this size is not routine tidying — it is the removal list for a future major, and the common theme is closing implicit conversions that silently change semantics. The performance and correctness work points the same way, toward the streaming engine as the default execution path rather than a mode: nested common subplan elimination, streaming grouped AsOf joins, hand-written Thrift for parquet metadata decode, and repeated fixes to sortedness and chunking on the streaming path. Cloud is the third leg, with the engine being taught to run against object storage without materializing.
◆ Prediction
With the streaming engine marked stable and this many APIs deprecated in a single wave, the deprecations are the visible countdown to a release that removes them. The entries do not say when, so the safer read is that the next Python releases keep pairing streaming-path fixes with further deprecation notices rather than breaking anything yet.
Citus
0.0ANALYTICS
Citus keeps three Postgres branches alive while chasing each new major
◆ Current state
Citus publishes synchronized maintenance releases across at least three live branches — 14.1, 13.3 and 12.1.13 all went out on the same day in July 2026 — with contents that are almost entirely backports of the same handful of upstream fixes. The substantive release in the window is Citus 14.0 from February, which added PostgreSQL 18.1 support. Release titles are inconsistent, several carrying release dates that contradict their publication date.
◆ Where it's heading
The pattern is a distributed-Postgres extension whose roadmap is set by Postgres itself: a major Citus version tracks a major Postgres version, then a long tail of branch releases carries fixes backward to users who cannot upgrade. Recent backport content is concentrated on correctness in edge cases — role propagation with missing grantor dependencies, deadlocks when adding named constraints with long partition names, crashes in CREATE STATISTICS — plus tightening ownership checks on citus-internal UDFs.
◆ Prediction
Expect the next Citus major to line up with the next PostgreSQL major, with 12.1 continuing to receive backports until it is retired. The entries do not indicate which branch is nearest end-of-life.
Alternatives to Polars and Citus
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Polars or Citus.
Apache Kylin
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Apache Iceberg
Iceberg's release cadence is now backports and CVE patches across three live minor lines.
Mage
Feature releases every two months in 2024; one bugfix release in the last twelve.
OpenMetadata
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
TimescaleDB
Every release in this window is columnstore work — compression is where TimescaleDB is spending
See all Polars alternatives → · See all Citus alternatives →
Recent activity from Polars and Citus
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoPolarsPolars 1.43.2: scan_csv schema inference, more casts deprecated
- 6d agoPolarsPolars 1.43.1: callback sinks on cloud, streaming and lakehouse scan fixes
- 12d agoPolarsPolars 1.43.0 deprecates categorical casts, profile() and implicit conversions
- 1mo agoCitusCitus 14.1 backport release
- 1mo agoCitusDeadlock, crash and role-propagation fixes for 12.1
- 1mo agoCitusCitus 13.3 backport release
- 1mo agoPolarsPolars 1.42.1: parquet metadata sampling and IO tweaks
- 1mo agoPolarsPolars 1.42.0: cloud IO concurrency control and streaming throughput
- 1mo agoPolarsRust Polars 0.54.4 stabilizes the streaming engine ⚡
- 5mo agoCitusCitus 14.0 adds PostgreSQL 18.1 support ⚡
Frequently asked questions
What is the difference between Polars and Citus?
They serve adjacent needs but don't currently overlap on shipped themes. Polars is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Polars better than Citus?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Polars is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to Polars?
Top Polars alternatives in Analytics are ranked by recent ship velocity. Browse the "Polars alternatives" section above for the current picks, or visit /alternatives/polars for the full list with editorial commentary on each.
What are the best alternatives to Citus?
Top Citus alternatives in Analytics are ranked by recent ship velocity. Browse the "Citus alternatives" section above for the current picks, or visit /alternatives/citus for the full list with editorial commentary on each.