Skip to content

GoldenMatch

v0.7.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 4mo Data Pipelines & ETL
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

data-cleaning data-engineering data-matching data-quality deduplication entity-resolution
+14 more
fellegi-sunter fuzzy-matching knowledge-graph llm master-data-management mcp-server polars pprl python record-linkage rust splink typescript zero-config

Summary

AI summary

GoldenMatch adds optional Ray backend for scaling deduplication to 10M+ records.

Full changelog

Ray Backend for Large-Scale Entity Resolution

GoldenMatch now scales to 10M+ records with an optional Ray backend.

pip install goldenmatch[ray]
goldenmatch dedupe huge_dataset.parquet --backend ray

Or in config:

backend: ray

Zero configuration needed. Ray auto-starts locally and uses all CPU cores. For datasets over 50M records, point at a Ray cluster.

| Records | Backend | User Setup |
|---------|---------|------------|
| < 500K | Polars (default) | Nothing |
| 500K - 2M | DuckDB or Ray local | pip install goldenmatch[ray] |
| 2M - 50M | Ray local | Same |
| 50M+ | Ray cluster | User provides infra |

How it works

Block scoring (the bottleneck) is distributed as independent Ray tasks. Each block is scored on a separate CPU core. Results are collected and merged into the pipeline seamlessly.

For small workloads (<= 4 blocks), falls back to the existing ThreadPoolExecutor automatically.

Stats

  • 909 tests passing (6 new)
  • CI green on Python 3.11/3.12/3.13
pip install --upgrade goldenmatch

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track GoldenMatch

Get notified when new releases ship.

Sign up free

About GoldenMatch

All releases →

Related context

Related tools

Earlier breaking changes

  • v3.1.0 `GOLDENMATCH_FRAME=polars` now requires the `[polars]` extra; raises error without it.
  • vgoldencheck-v3.0.0 `inferred_type` emits neutral dtype vocabulary (str/int/uint/float/date/datetime/bool/other) instead of raw Polars dtypes.
  • vgoldencheck-v3.0.0 'inferred_type' now emits a neutral dtype vocabulary instead of raw Polars dtype strings.
  • vgoldencheck-v3.0.0 `scan_file`, `scan_dataframe`, and CLI `check` now run without Polars, using Arrow-native pyarrow.Table.
  • v3.0.0 Result frames now return pyarrow.Table instead of Polars DataFrame.

Beta — feedback welcome: [email protected]