silx
silx settles into maintenance a release after its PySide6 migration
A side-by-side editorial comparison of hubAdmin and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
The config-authoring half of hubverse, pinned to whatever the schema is doing this quarter
hubAdmin builds and validates the JSON configuration that defines a hubverse forecast hub — rounds, model tasks, output types, target metadata. It is the administrator-facing member of the hubverse family, sitting alongside the packages that read and evaluate hub data. Its release cadence is set almost entirely by the hubverse schema, which it has now tracked from v4.0.0 through v6.0.0.
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
hubAdmin builds and validates the JSON configuration that defines a hubverse forecast hub — rounds, model tasks, output types, target metadata. It is the administrator-facing member of the hubverse family, sitting alongside the packages that read and evaluate hub data. Its release cadence is set almost entirely by the hubverse schema, which it has now tracked from v4.0.0 through v6.0.0.
Every release here is legible as schema-following. New schema properties become new arguments, new schema constraints become new validate_config() checks, and the package version is essentially a marker for which schema generation it can author. The one thread that is genuinely its own is ergonomics: session-level options for schema version and branch, support for in-development schema branches, and a steadily stricter validator that now catches duplicate properties and mismatched target keys before a hub goes live.
With v6.0.0 support only partially landed, the next releases most likely finish the additional_metadata migration across the remaining create_* functions.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
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 hubAdmin or TimescaleDB.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
See all hubAdmin alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB 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.
Top hubAdmin alternatives in Analytics are ranked by recent ship velocity. Browse the "hubAdmin alternatives" section above for the current picks, or visit /alternatives/hubadmin for the full list with editorial commentary on each.
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.