[
https://issues.apache.org/jira/browse/NIFI-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124461#comment-16124461
]
ASF GitHub Bot commented on NIFI-4142:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2015
went ahead and fixed the typo and squashed locally.
Ran a test flow that created csv of various conformity to a simple spec.
Ran it through various configratuions of the validator and it behaved as
desired and expected in each case. When data was marked invalid was able to
see precisely why through the provenance events which was great. Was able to
see coercion/non-coercion behavior and all checks out.
+1 merging to master
> Implement a ValidateRecord Processor
> ------------------------------------
>
> Key: NIFI-4142
> URL: https://issues.apache.org/jira/browse/NIFI-4142
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.4.0
>
>
> We need a processor that is capable of validating that all Records in a
> FlowFile adhere to the proper schema.
> The Processor should be configured with a Record Reader and should route each
> record to either 'valid' or 'invalid' based on whether or not the record
> adheres to the reader's schema. A record would be invalid in any of the
> following cases:
> - Missing field that is required according to the schema
> - Extra field that is not present in schema (it should be configurable
> whether or not this is a failure)
> - Field requires coercion and strict type checking enabled (this should also
> be configurable)
> - Field is invalid, such as the value "hello" when it should be an integer
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
