tJSONValidator Standard properties

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

The Standard tJSONValidator component belongs to the Data Quality family.

Basic settings

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. Click Sync columns to retrieve the schema from the previous component connected in the Job. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available: View schema: choose this option to view the schema only. Change to built-in property: choose this option to change the schema to Built-in for local changes. Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.
	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.
Allocate	Define the schema against which the data of each column must be validated. The schema can be a local file or a HTTP protocol.
Die on error	Select the check box to stop the execution of the Job when an error occurs. Clear the check box to skip any error and continue the Job execution process.

tStatCatcher Statistics	Select this check box to gather the Job processing metadata at the Job level as well as at each component level.
JSON schema draft version	Select the version to be used when $schema is not defined in the JSON schema. This option is ignored when $schema is defined.
JSON schema file encoding	Select the encoding from the drop-down list.
Custom encoding	This option is available when Other is selected as JSON schema file encoding. Enter the encoding name.

Usage rule	This component is used as an intermediate step. It requires an input and output flows.

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