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

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

Github user pvillard31 commented on the issue:

    https://github.com/apache/nifi/pull/476
  
    Hey @JPercivall, I think I've addressed most of your comments:
    - changed log level
    - fixed decrementation (was not related to header but rather to 'finally' 
in 'while' loop)
    - strategy naming and description
    - fixed first line handling and added a unit test for that and to confirm 
Unique() behavior when validating line by line
    - changed exception catching
    
    It remains what you observed when displaying content of flow files after 
being processed by the processor. I've reproduced your observation but I didn't 
find any explanation. By any chance, do you know if there are some specific 
encoding related to the UI display? (I remember some discussions regarding how 
is processed the carriage return (shift + enter instead of \n) when used in a 
property in some processors) If you haves ideas, let me know!
    
    Thanks.


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