[
https://issues.apache.org/jira/browse/NIFI-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383284#comment-15383284
]
ASF GitHub Bot commented on NIFI-1942:
--------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/476
@pvillard31, sorry for not realizing this earlier but a great improvement
that could be made is to route like RouteText does. Where it can either route
the whole FlowFile when it fails or route each line to the respective
valid/invalid destination. Where invalid rows would have an attribute detailing
what went wrong.
I believe all that would need to be done is to create flowfiles with each
reading of the row and if it fails add it to the invalid list (along with
adding an attribute to it).
> Create a processor to validate CSV against a user-supplied schema
> -----------------------------------------------------------------
>
> Key: NIFI-1942
> URL: https://issues.apache.org/jira/browse/NIFI-1942
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: ValidateCSV.xml
>
>
> In order to extend the set of "quality control" processors, it would be
> interesting to have a processor validating CSV formatted flow files against a
> user-specified schema.
> Flow file validated against schema would be routed to "valid" relationship
> although flow file not validated against schema would be routed to "invalid"
> relationship.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
