Data Validator

Transform

This Snap provides the functionality to validate incoming data against a set of defined constraints.
Available constraints are:

• Pattern

• Minimum

• Maximum

• MinLength

• MaxLength

• Required

• Type

An example of a pattern can be seen in the following image:

Open

The pattern constraint in the screenshot above validates all incoming documents and their attributes a.c.b against the regular expression ^abc, expecting that all attribute values of a.c.b start with abc. If they do, the document is routed to the output view; otherwise, the document is routed to the error view.

• Pattern is a regular expression, defined as a string value.

• Minimum and Maximum can only be defined for number values. Allowed constraint values are numbers. 

• MinLength and MaxLength can only be defined for string values. Allowed constraint values are integers. 

• Required can be defined for any value and will verify that a value exists. The Constraint value field is ignored for the Required constraint.

• Type can be defined for any source path. The default is object. Valid type definitions are: string, number, object, array, boolean, date, time, date-time, local-date-time, any.

N/A

Works in Ultra Tasks.

The Data Validator Snap displays an error if the required field is set to true and no object is passed from the upstream.

Workaround: To validate null or empty values, you can either set a Minimum length Constraint of 1, or use the regex pattern ^.+$“

This Snap does not use accounts.

Required. The name for the Snap. You can modify it to be more specific, especially if you have more than one of the same Snap in your Pipeline.

Define constraints for one or more fields. If multiple constraints are defined for the same field using the same constraint, only the first definition is considered.

Available options are: 

• Pattern

• Minimum

• Maximum

• MinLength

• MaxLength

• Required

• Type

Default value: N/A

Examples:

Select this property to enable the Snap to verify if all parents in the JSON path exist, and produce an error if all parents do not exist.

Example:

When there is only one Constraint Required=true for a Source path=$a.c.b, but an input document is as follows:

The Snap does not produce an error if this property is not selected, even if the JSON path $a.c.b has no values unless there is another Constraint Required=true for a Source path=$a.c.

If this property is selected, the Snap produces an error with a reason field. Example, Path not found: $.a.c, Source path: $.a.c.b, Constraint: Required=true.

Default value: Unselected

If true, the Snap produces the error document in standard error format (error, reason, original, and stack trace). If false, the error document contains error and original.

Default value: False

Select one of the three modes in which the Snap executes. Available options are:

• Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

• Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

• Disabled: Disables the Snap and all Snaps that are downstream from it.

Default Value: Execute only
Example: Validate & Execute