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

ASF subversion and git services commented on NIFI-9701:
-------------------------------------------------------

Commit 2fbe10b4bc246eaec8ab289d88f7cf3b46b75496 in nifi's branch 
refs/heads/main from Nathan Gough
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2fbe10b ]

NIFI-9701 - Corrected No Tracking strategy to create one flow file when using a 
Record Writer

- Corrected No Tracking strategy Record Writer handling for ListSFTP
- Updated temporary test files to have last modified time of epoch to avoid 
intermittent issue with Minimum Age filtering
- Refactored MockCacheService to separate reusable class

This closes #5885

Signed-off-by: David Handermann <[email protected]>


> ListSFTP creates separate flowfiles when recordwriter is defined and Listing 
> Strategy is "No Tracking"
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-9701
>                 URL: https://issues.apache.org/jira/browse/NIFI-9701
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.15.3
>         Environment: Linux / GCP
>            Reporter: Armin Aschoff
>            Assignee: Nathan Gough
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> SFTP server has multiple files in nominated directory.
> Configure ListSFTP with a recordwriter and Listing Strategy of "Tracking 
> Entities", ListSFTP creates a single flowfile with content containing records 
> of all found entities.  This is as expected.
> Then, by simply changing the Listing Strategy to "No Tracking", ListSFTP 
> creates one flowfile per found entity.  This should not happen - ListSFTP 
> should still produce only one flowfile with content containing records of all 
> found entities.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to