Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

tSchemaComplianceCheck Standard properties

These properties are used to configure tSchemaComplianceCheck running in the Standard Job framework.

The Standard tSchemaComplianceCheck component belongs to the Data Quality family.

The component in this framework is available in all Talend products.

Basic settings

Properties Description

Base Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

It describes the structure and nature of your data to be processed as it is. Used by both Basic Checks and Advanced JSON Schema modes.

Built-In: You create and store the schema locally for this component only.

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

Check all columns from schema

Select this option to carry out all checks on all columns against the base schema.

Custom defined

Select this option to carry out particular checks on particular columns. When this option is selected, the Checked Columns table shows.

Checked Columns

In this table, define what checks are to be carried out on which columns. This table appears when you select the Custom defined option.

  • Column: Displays the columns names.

  • Type: Select the type of data each column is supposed to contain. This validation is mandatory for all columns.

  • Date pattern: Define the expected date format for each column with the data type of Date.

  • Nullable: Select the checkbox in an individual column to define the column to be nullable, that is, to allow empty rows in this column to go to the output flow regardless of the base schema definition. To define all columns to be nullable, select the checkbox in the table header.

  • Max length: Select the checkbox in an individual column to verify the data length of the column against the length definition of the base schema. To carry out this verification on all the columns, select the checkbox in the table header.

Use another schema for compliance check

In order to reject the non-compliant data, define a reference schema as you expect the data to be.

It can be restrictive on data type, null values, and length.
Check columns from a JSON schema URI

This option is available from Talend Studio 8.0 R2026-05 onwards.

Select this option to validate the data against a JSON schema.

Enter the JSON schema URI in double quotes.

Trim the excess content of column when length checking chosen and the length is greater than defined length

Select this checkbox to truncate the data that exceeds the length specified rather than reject it.

Information noteRestriction:

This option is applicable only on data of String type.

This option is not available when Check columns from a JSON schema URI is selected.

Advanced settings

The advanced settings depends on the Mode selected in the Basic settings.

This table describes the advanced settings when Check columns from a JSON schema URI is selected
Properties Description

JSON schema draft version

Select the draft version to use. For more information, see json-schema.org

JSON schema file encoding

Select the encoding of the schema file.
This table describes the advanced settings when Check columns from a JSON schema URI is not selected
Properties Description

Use Fastest Date Check

Select this checkbox to perform a fast date format check using the TalendDate.isDate() method of the Talend Date system routine if Date pattern is not defined. For more information about routines, see What are routines.

Use Strict Data Check

Select this checkbox to perform a strict data format check. When selected, the Use Fastest Data Check checkbox is hidden.

Ignore TimeZone when Check Date

Select this checkbox to ignore the time zone setup upon date check.

This option is not available when Check all columns from schema is selected.

Treat all empty string as NULL

Select this checkbox to treat any empty fields in any columns as null values, instead of empty strings.

By default, this checkbox is selected. When it is cleared, the Choose Column(s) table shows to let you select individual columns.

Check string by byte length

Select this checkbox to check the string column with byte length according to the charset set in the Charset text box.

By default, this checkbox is not selected and only character length is checked.

tStatCatcher Statistics

Select this checkbox 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 checkbox is cleared, if the component has this checkbox.

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.

Schema violations output

When Check columns from a JSON schema URI is selected, the component validates data against a JSON schema with advanced constraints, invalid rows are sent to the Rejects flow with structured violation metadata.

Information Description
All input columns Pass-through from input. All input column values are preserved unchanged in the Rejects flow.
ErrorType Type of the error.

ErrorCode

Code identifying the type of schema violation encountered.

ErrorMessage

Error message summarizing the violation.

Usage

Usage guidance Description

Usage rule

This component is an intermediary step in the flow allowing to exclude from the main flow the non-compliant data. This component cannot be a start component as it requires an input flow. It also requires at least one output component to gather the validated flow, and possibly a second output component for rejected data using Rejects link. For more information, see Rejects.

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 – please let us know!

Leave your feedback here