wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A side-by-side editorial comparison of Databricks and dqcheckr — release velocity, themes, recent moves, and the top alternatives to consider.
Databricks lands DBR 18.2 GA on Spark 4.1; the 18.x line is the active story, older LTS pages are mostly doc refreshes.
The substantive shipping event in the window is Databricks Runtime 18.2 GA on May 4, the latest minor in a fast 18.x cadence on Spark 4.1.0 (18.0 in January, 18.1 in March, 18.2 Beta on April 8, GA on May 4). The rest of the recent feed is an April 13 documentation refresh that updated release notes for older LTS versions — 14.3, 15.4, 16.4, 17.3, 13.3 — without new shipping behind them.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
The substantive shipping event in the window is Databricks Runtime 18.2 GA on May 4, the latest minor in a fast 18.x cadence on Spark 4.1.0 (18.0 in January, 18.1 in March, 18.2 Beta on April 8, GA on May 4). The rest of the recent feed is an April 13 documentation refresh that updated release notes for older LTS versions — 14.3, 15.4, 16.4, 17.3, 13.3 — without new shipping behind them.
Databricks is pushing Spark 4.1 hard through the runtime line: JDK 21 default in 18.x, breaking changes around NULL preservation and partition columns, aggressive deprecation of older behaviors (input_file_name removal, AWS SDK v1 shading). The 18.x cadence is roughly one minor every six weeks, and 16.4 LTS is acting as the bridge for customers needing to migrate Scala 2.12 code to 2.13 before they can move to 17 or 18.
Expect an 18.x LTS designation later in 2026 once the line stabilizes, with continued behavioral hardening and more shaded dependency cleanup. Doc refreshes for older LTS versions — particularly 13.3 LTS, which is close to its August 2026 end-of-support — will likely keep landing as Databricks pushes customers up the runtime stack.
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
Both moves point the same way: reduce what the operator has to write and know. Config generation removes the hand-authored YAML that gated first use, list_runs() and validate_config() make an existing setup inspectable, and the snapshot comparison turns accumulated run history into a second product surface. Check coverage keeps widening underneath — outlier detection, composite keys, row-count and file-size ceilings — and the reporting layer moved from rmarkdown to Quarto, with existing 0.1.x databases auto-migrated on first run.
Expect the generated configs and the drift reports to converge, so a sniffed config can seed thresholds from the snapshot history rather than from defaults, plus continued growth in the numbered QC check catalogue.
Other Infra & APIs 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 Databricks or dqcheckr.
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
See all Databricks alternatives → · See all dqcheckr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Databricks is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. Databricks is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Databricks alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Databricks alternatives" section above for the current picks, or visit /alternatives/databricks for the full list with editorial commentary on each.
Top dqcheckr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dqcheckr alternatives" section above for the current picks, or visit /alternatives/dqcheckr for the full list with editorial commentary on each.