[ 
https://issues.apache.org/jira/browse/NIFI-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Villard resolved NIFI-13333.
-----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 
1.x release line. Marking as resolved as part of a cleanup operation. Please 
open a new one with an updated description if this is still relevant for NiFi 
2.x.

> ParseEVTX Processor does not pass failed flow files to failure relationship
> ---------------------------------------------------------------------------
>
>                 Key: NIFI-13333
>                 URL: https://issues.apache.org/jira/browse/NIFI-13333
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.24.0
>         Environment: Docker
>            Reporter: Stephen Jeffrey Hindmarch
>            Priority: Major
>
> As noted in NIFI-13332, when the ParseEVTX fails to parse a file, eg if the 
> file has the wrong minor version, the flow file is not passed to the failure 
> relationship, but instead remains on the incoming relationship with a penalty 
> and is repeatedly parsed.
> This seems like a poor behaviour choice, as there is nothing that is going to 
> change about that incoming file that will allow it to be parsed.
> For example, generate a test flow with some simple text content, egĀ 
> {code:java}
> <Data>Not an EVTX File</Data>{code}
> Then send this to a ParseEVTX processor. The parser will keep penalising the 
> flow file and keep it on the incoming queue with this error message.
> {noformat}
> ParseEvtx[id=c5eadd74-56b2-3763-b7d0-1274b905ce06] Processing failed: 
> org.apache.nifi.processor.exception.ProcessException: IOException thrown from 
> ParseEvtx[id=c5eadd74-56b2-3763-b7d0-1274b905ce06]: java.io.IOException: 
> Expected null terminated string
> - Caused by: java.io.IOException: Expected null terminated string{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to