Blocking Strategies: DEFAULT vs WIDER
Choose between DEFAULT and WIDER blocking strategies to control how Zingg orders candidate fields when building the blocking tree.
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 yourfieldDefinitionlist 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.

When to use which
Configure
Set blockingModel right after labelDataSampleSize when building your Enterprise arguments object.
Last updated
Was this helpful?