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

Pierre Villard resolved NIFI-8425.
----------------------------------
    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.

> ListFile Processor doesn't batch when Listing Strategy is No Tracking
> ---------------------------------------------------------------------
>
>                 Key: NIFI-8425
>                 URL: https://issues.apache.org/jira/browse/NIFI-8425
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.13.2
>            Reporter: Chris
>            Priority: Major
>         Attachments: image-2021-04-13-14-35-50-488.png, 
> image-2021-04-13-14-39-06-024.png
>
>
> I was looking to do some batch processing with the list processor (didn't 
> have a better option :()  Per NiFi documentation I was looking to set the 
> Record Writer using Avro Writer so that I could get a complete listing in a 
> single flow file.
> !image-2021-04-13-14-39-06-024.png|width=411,height=287!
>  
> I didn't see any indication in the documentation that anything other than 
> associating a record writer would determine if a single or multiple flow was 
> generated. !image-2021-04-13-14-35-50-488.png|width=666,height=408!
>  
> *Use Case*
> I wanted to get a complete listing, if it didn't include a file (file we've 
> specified as a trigger for completion of batch) I would drop the entire flow. 
> If it did include the file I was waiting for i'd split out the list of files 
> and fetch all of them. 
> If tracking is used then the future flows don't contain the entire list and 
> this requires me to maintain the listing of files that will need to be picked 
> up. So if no tracking was an option it would work in a simpler fashion.



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

Reply via email to