Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Configuring data quality computing

Once you have computed data quality on your dataset for the first time, you have the possibility to refresh this calculation and customize it according to your needs.

Selecting the sample size and processing mode

To be able to customize the sample size for quality computing, you need to have previously clicked Compute once on your dataset.

  1. From Qlik Talend Data Integration > Catalog, open your dataset.

  2. Click Refresh.

    The Quality and profiling window opens.

  3. In Sample size, enter the size of the sample on which you want to calculate data quality:

    • Number of rows: Enter the number of rows on which you want to calculate data quality. The maximum value is 100000 rows in pullup mode, there is no maximum value in pushdown mode.

    • Percentage of the dataset: Alternatively, enter the percentage of the dataset on which you want to calculate data quality. Decimal values are not allowed. For big datasets, if 1% of the dataset equals more than the maximum number of rows allowed (100000 rows), this option is not displayed.

  4. In Processing mode, select the processing mode to use when calculating data quality:

    • Pushdown: Currently only available for Snowflake datasets. It triggers the quality computation on Snowflake side, costing Snowflake credits.

    • Pullup: Available for all datasets. It triggers the quality computation in Qlik Cloud.

  5. Click Refresh to recompute the data quality according to your settings.

The data quality indicators as well as the sample size are displayed in the Overview. The processing time varies depending on the sample size. Note that the data preview always displays 100 records only.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!