Hey Rifat – cool idea. Is the ListS3 processor something we wrote? Or are you suggesting contributing to Nifi itself?
From: "Chowdhury, Rifat" <[email protected]> Date: Wednesday, March 18, 2020 at 2:45 PM To: "[email protected]" <[email protected]> Cc: "Loyot, Brendan" <[email protected]>, "Nagwani, Dheeraj X. -ND" <[email protected]>, "Evans, Jason D." <[email protected]>, "Rudra, Anshuman X. -ND" <[email protected]> Subject: Nifi Enhancement Idea Hi, For processors such as ListS3, would it be beneficial to add a new field called “suffix” so that when I configure my ListS3 processor, I can filter my incoming files furthers in addition to prefix? The current Template I follow is ListS3 -> RouteOnAttribute(filename endsWith my suffix criteria) Like if I want to filter for only .csv or .tsv or .gz or .txt files or any other types of files. Or another Option is have prefix field accept some sort of Java REGEX Pattern matching. What do you guys think? Shall I create a PR for this against Nifi Branch for future releases? I don’t feel the need to create a custom processor for this rather small enhancement. Best Regards, Rifat Chowdhury Software Engineer, Data Platforms [signature_1999449656] THE WALT DISNEY COMPANY | DIRECT-TO-CONSUMER AND INTERNATIONAL [email protected]<mailto:[email protected]>
