[ 
https://issues.apache.org/jira/browse/NIFI-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383124#comment-15383124
 ] 

ASF GitHub Bot commented on NIFI-1942:
--------------------------------------

Github user pvillard31 commented on the issue:

    https://github.com/apache/nifi/pull/476
  
    Hey @JPercivall 
    - Reverted NOTICE changes
    - Separated the exception and changed the logging approach when there is an 
invalid CSV
    - Changed the error message when the user provides a wrong method in the 
schema property and added a test (let me know in case it is not what you were 
thinking about)
    - Added IsIncludedIn cell processor (my bad!).
    - Added list of supported cell processors in additional documentation.
    
    For the other cell processors I am not sure to see how they would fit in a 
validating process. If I am missing something here, let me know. There are 
interesting cell processors to modify CSV content by writing a new CSV file (a 
new FlowFile). This could be nice but this is not only validation anymore, I 
assume this would be better in a different processor, no?


> 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)

Reply via email to