ValidateJson 2.3.0¶
BUNDLE¶
org.apache.nifi | nifi-standard-nar
DESCRIPTION¶
Validates the contents of FlowFiles against a configurable JSON Schema. See json-schema.org for specification standards. This Processor does not support input containing multiple JSON objects, such as newline-delimited JSON. If the input FlowFile contains newline-delimited JSON, only the first line will be validated.
INPUT REQUIREMENT¶
REQUIRED
Supports Sensitive Dynamic Properties¶
false
PROPERTIES¶
Property |
Description |
---|---|
JSON Schema |
A URL or file path to the JSON schema or the actual JSON schema content |
JSON Schema Registry |
Specifies the Controller Service to use for the JSON Schema Registry |
JSON Schema Version |
The JSON schema specification |
Max String Length |
The maximum allowed length of a string value when parsing the JSON document |
Schema Access Strategy |
Specifies how to obtain the schema that is to be used for interpreting the data. |
Schema Name |
Specifies the name of the schema to lookup in the Schema Registry property |
RESTRICTIONS¶
REQUIRED PERMISSION |
EXPLANATION |
---|---|
reference remote resources |
Schema configuration can reference resources over HTTP |
RELATIONSHIPS¶
NAME |
DESCRIPTION |
---|---|
failure |
FlowFiles that cannot be read as JSON are routed to this relationship |
valid |
FlowFiles that are successfully validated against the schema are routed to this relationship |
invalid |
FlowFiles that are not valid according to the specified schema are routed to this relationship |
WRITES ATTRIBUTES¶
NAME |
DESCRIPTION |
---|---|
json.validation.errors |
If the flow file is routed to the invalid relationship , this attribute will contain the error message resulting from the validation failure. |