# tBlockedFuzzyJoin Availability-note[Deprecated](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-deprecated) This content is deprecated. Information noteImportant: This component is deprecated since the 6.0 General Availability release and removed from Talend Studio 8.0 R2024-05 onwards. Talend recommends to use the tRecordMatching component. Helps ensuring the data quality of any source data against a reference data source. tBlockedFuzzyJoin joins two tables by doing a fuzzy match on several columns. It compares columns from the main flow with reference columns from the lookup flow and outputs the match data, the possible match data and the rejected data. ## tBlockedFuzzyJoin Standard properties These properties are used to configure tBlockedFuzzyJoin running in the Standard Job framework. The Standard tBlockedFuzzyJoin component belongs to the Data Quality family. This component is available in Talend Data Management Platform, Talend Big Data Platform, Talend Real-Time Big Data Platform, Talend Data Services Platform and in Talend Data Fabric. ## Basic settings | Properties | Description | | --- | --- | | Schema and
Edit Schema |

A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository.
Built-in: You create and store the schema locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.
Repository: You have already created and stored the schema in the Repository. You can reuse it in other projects and Job designs. For more information about a component schema in its Basic settings tab, see Basic settings tab.

| | Replace output column with lookup
column if matches or possible
matches | Select this check box to replace the output
column with the lookup column in case of match or
possible match values. | | Input key
attribute | Select the column(s) from the main flow that
needs to be checked against the reference (lookup)
key column. | | Lookup key
attribute | Select the lookup key columns that you will
use as a reference against which to compare the
columns from the input flow. | | Matching type | Select the relevant matching algorithm from
the list:

Exact Match:
matches each processed entry to all possible
reference entries that have exactly the same
value.

Levenshtein:
Based on the edit distance theory. It calculates
the number of insertion, deletion or substitution
required for an entry to match the reference
entry.

Metaphone: Based
on a phonetic algorithm for indexing entries by
their pronunciation. It first loads the phonetics
of all entries of the lookup reference and checks
all entries of the main flow against the entries
of the reference flow.

Double Metaphone:
a new version of the Metaphone phonetic algorithm,
that produces more accurate results than the
original algorithm. It can return both a primary
and a secondary code for a string. This accounts
for some ambiguous cases as well as for multiple
variants of surnames with common ancestry. | | Case sensitive | Select this check box to consider the letter
case. | | Min. distance | Only for Levenshtein. Set the minimum number of
changes allowed to match the reference. If set to
0, only perfect matches(Exact Match) are returned.

Information noteNote:

You can create and store context variables
for the minimum and maximum distances and then
have your Job to loop on these values in order to
start from a low max number to match rows and go
up to higher max number to match more possible
rows. You can press Ctrl+Space to access the variable list
and select the new context variables. For more
information about context variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | | Max. distance | Only for Levenshtein. Set the maximum number of
changes allowed to match the reference. | ## Advanced settings | Properties | Description | | --- | --- | | tStat
Catcher
Statistics | Select this check box to collect log data at
the component level. | ## Global Variables | Variables | Description | | --- | --- | | Global
Variables | ERROR\_MESSAGE: the error message generated by the component when an
error occurs. This is an After variable and it returns a string. This variable functions
only if the Die on error check box
is cleared, if the component has this check
box.

A Flow variable functions during the execution of a component
while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from
it.

For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component is deprecated, use the tRecordMatching
component instead.

This component is not startable (green
background) and it requires two input components
and one or more output components. |