# Configuring the match analysis

Available in...

* Big Data Platform
* Cloud API Services Platform
* Cloud Big Data Platform
* Cloud Data Fabric
* Cloud Data Management Platform
* Data Fabric
* Data Management Platform
* Data Services Platform
* Qlik Talend Cloud Enterprise Edition
* Qlik Talend Cloud Premium Edition
* Real-Time Big Data Platform

## Procedure

1. In the Limit field, set the number for the data records you want to use as a data sample.

   ![Screenshot of the Match Analysis view.](https://help.qlik.com/talend/en-US/studio-user-guide/Resources/images/match_analysis2.png)
2. Optional: Click any column name in the table to sort the sample data in an ascending or descending order.
3. In the match analysis editor, configure the options.
   | Option | Purpose |
   | --- | --- |
   | ![Show in Data Quality repository](https://help.qlik.com/talend/en-US/studio-user-guide/Resources/images/repository_nav.svg) | Locate the selected table under the<br>Metadata node in the tree<br>view. |
   | New Connection | Create a connection to a database or to a file from<br>inside the match analysis editor where you can expand this<br>new connection and select the columns on which to do the<br>match.<br><br>For further information about how to create a<br>connection to data sources, see [Creating connections to data sources](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/creating-connections-to-data-sources). |
   | Select Data | Update the selection of the columns listed in the<br>table.<br><br>If you change the dataset for an analysis, the<br>charts that display the match results of the sample data<br>will be cleared automatically. You must click<br>Chart to compute the match<br>results for the new dataset you have<br>defined. |
   | Refresh Data | Refresh the view of the columns listed in the<br>table. |
   | n first rows<br><br>or<br><br>n random rows | List in the table N first data records from the selected<br>columns or list N random records from the selected<br>columns. |
   | Select Blocking Key | Define the columns from the input flow according to which<br>you want to partition the processed data in blocks.<br><br>For<br>more information, see [Defining a match rule](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/defining-match-rule). |
   | Select Matching Key | Define the match rules and the columns from the input<br>flow on which you want to apply the match algorithm.<br><br>For<br>more information, see [Defining a match rule](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/defining-match-rule). |
   | Store on disk | Store processed data blocks on the disk to maximize system performance.<br><br><br>Max buffer size: Type in the size<br>of physical memory you want to allocate to processed<br>data.<br><br><br>Temporary data directory path:<br>Set the path to the directory where the temporary file<br>must be stored.<br><br><br>Allow drill down: Select to store<br>locally the data that will be analyzed by the current<br>analysis. It will enable the View<br>rows feature from the<br>Settings menu. It displays a<br>list of duplicate rows or groups of the same size. For<br>more information, see [Viewing and exporting the analyzed data](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/viewing-the-anaylzed-data). |

## Results

The Data Preview table has additional columns that show the results of matching data:

* GID: represents the group identifier.

* GRP\_SIZE: counts the number of records in the group, computed only on the master record.

* MASTER: identifies, by true or false, if the record used in the matching comparisons is a master record. There is only one master record per group.

  Each input record will be compared to the master record, and if they match, the input record will be in the group.

* SCORE: measures the distance between the input record and the master record according to the matching algorithm used.

* GRP\_QUALITY: only the master record has a quality score which is the minimal value in the group.

* ATTRIBUTE\_SCORE: lists the match score and the names of the columns used as key attributes in the applied rules.