Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Enterprise only

Blocking Strategies: DEFAULT vs WIDER

Choose between DEFAULT and WIDER blocking strategies to control how Zingg orders candidate fields when building the blocking tree.

Enterprise only. Controlled by the blockingModel config key (DEFAULT or WIDER, case-insensitive). If omitted, Zingg uses DEFAULT. Community/OSS has no such key - it always behaves like DEFAULT.

What each strategy does

Zingg builds a blocking tree greedily. At every node it asks: of the eligible field/hash-function combinations, which one splits the group into smaller pieces? That combination becomes the split at this node, and the process recurses into each resulting group.

The strategy controls only the order candidate fields are offered at each node - never the comparison logic itself:

  • DEFAULT - every node is offered your fieldDefinition list in the exact order you configured it. The field listed first is always tried first, everywhere in the tree.

  • WIDER - each node looks at which field its parent node just used, and pushes that field to the back of the candidate list for this node, so the very next field in line gets first consideration instead. This repeats going down the tree, so the field that "won" one level isn't automatically favored again immediately below it.

DEFAULT vs WIDER field ordering down the blocking tree
DEFAULT vs WIDER field ordering down the blocking tree

When to use which

Use DEFAULT when your fields have very different discriminating power

If one field (for example, a national ID or a well-populated postcode) is consistently the best splitter for your data, DEFAULT lets that field win at every node where it's eligible. This produces a narrower, more predictable tree built around your strongest signal.

Use WIDER when several fields have similar discriminating power

If your first field only slightly outperforms the second and third (for example, fname, lname, and city all split the data reasonably well), DEFAULT can end up leaning on the same field repeatedly down consecutive levels, producing a tree that is deep in one dimension and under-uses the others. WIDER forces the next-best field into consideration at the child node, spreading splits across more fields and typically producing a wider, shallower tree.

Use WIDER if verifyBlocking shows large, low-specificity blocks

Large blocks with DEFAULT are a symptom of the tree over-relying on one or two fields. Try WIDER and re-run verifyBlocking to compare block-size distribution and coverage before committing to the change.

Configure

Set blockingModel right after labelDataSampleSize when building your Enterprise arguments object.

Last updated

Was this helpful?