Github user jtstorck commented on the issue:
https://github.com/apache/nifi/pull/2930
@bbende @joewitt
This PR changes the default behavior of how the filter is applied during a
listing, which might require manual migration efforts for some users.
We could add a property to be able to toggle the application of the filter
to directory and file names or filenames only, with the default being directory
and file names. This solution would preserve the current behavior, and allow
users to "opt-in" to having recursive listings retrieve all files regardless of
directory names. There would not be an issue with migration for current users
that depend on the current behavior.
We could also go down the route of allowing the filter to be applied to the
entire path. That gives the user maximum flexibility on how the filter would
work, but requires more regex knowledge and is potentially harder for users to
write the filter they want. This would also require manual migration, but it
might be the best long-term solution. The tooltip on the filter property could
be updated to have an example regex that would provide the default
functionality that users could use as a starting point for custom filters.
Any thoughts on either of these solutions?
---
