Omni
Omni ships weekly, and almost every week the headline item is an AI feature
A side-by-side editorial comparison of Apache Cloudberry and OpenHouse — release velocity, themes, recent moves, and the top alternatives to consider.
An MPP warehouse fork grinding through ASF incubation, one release candidate at a time
Apache Cloudberry is a Greenplum-derived MPP data warehouse working through Apache incubation. Its release feed is procedural rather than editorial: each version ships as a tag with download links, checksum instructions and a contributor roll, while the actual changelog lives off-site on cloudberry.apache.org. The 2.1.0-incubating release in May 2026 is the most recent general release, preceded by two release candidates.
LinkedIn's Iceberg control plane, shipping one pull request per release.
OpenHouse is LinkedIn's open-source control plane for Iceberg tables, and it releases per merged pull request — version numbers climb several times a week with a single change each. The current work is concentrated on making the service defensible in production: a fix for CREATE OR REPLACE AS SELECT silently wiping table policies, request-ID correlation and a typed exception hierarchy in the data loader, and targeted scheduler logging for jobs observability.
Apache Cloudberry is a Greenplum-derived MPP data warehouse working through Apache incubation. Its release feed is procedural rather than editorial: each version ships as a tag with download links, checksum instructions and a contributor roll, while the actual changelog lives off-site on cloudberry.apache.org. The 2.1.0-incubating release in May 2026 is the most recent general release, preceded by two release candidates.
The cadence has shifted from the 2024 weekly-build era to a slower, more formal release train: two or three release candidates, then a general release roughly every eight months. That is the shape of a project optimizing for ASF graduation criteria — reproducible builds, signed artifacts, documented voting — rather than for feature velocity. The contributor list is broad and stable across releases, which suggests a real multi-vendor community rather than a single-sponsor project.
Expect a 2.2.0 release-candidate series to open on a similar multi-month cycle. Whether the project exits incubation in that window is not something these release notes indicate either way.
OpenHouse is LinkedIn's open-source control plane for Iceberg tables, and it releases per merged pull request — version numbers climb several times a week with a single change each. The current work is concentrated on making the service defensible in production: a fix for CREATE OR REPLACE AS SELECT silently wiping table policies, request-ID correlation and a typed exception hierarchy in the data loader, and targeted scheduler logging for jobs observability.
The theme across these releases is treating table metadata as something that must not be lost by accident, and making failures attributable. Policies now merge rather than being rebuilt from the request. Data loader errors carry a request ID and distinguish authentication from transport failure instead of retrying auth errors as transient. Feature toggles gained self-service table overrides so server-side ramps and table-owner opt-in can coexist.
The jobs-observability plan explicitly defers OTEL gauges, a heartbeat sampler, and DLQ counters to a later phase, so those are the concrete next steps visible in these entries.
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 Apache Cloudberry or OpenHouse.
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Amundsen's last release was a config flag, and the feed has been silent for two years
See all Apache Cloudberry alternatives → · See all OpenHouse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenHouse 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. OpenHouse 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 Apache Cloudberry alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache Cloudberry alternatives" section above for the current picks, or visit /alternatives/apache-cloudberry for the full list with editorial commentary on each.
Top OpenHouse alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenHouse alternatives" section above for the current picks, or visit /alternatives/openhouse for the full list with editorial commentary on each.