[
https://issues.apache.org/jira/browse/NIFI-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-7292:
---------------------------------
Fix Version/s: 1.12.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ListFile should skip elements without sufficient permissions
> ------------------------------------------------------------
>
> Key: NIFI-7292
> URL: https://issues.apache.org/jira/browse/NIFI-7292
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.9.2
> Reporter: Matthew Clarke
> Assignee: Simon Bence
> Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> I noticed that NiFi's ListFile processor (and probably other list based
> processors) will check permissions on sub-directories before it evaluates the
> path filter.
> Let's assume we have a mounted directory (/NiFi/mount) that contains sub
> directories (A, B, C, D, and private). The NiFi Service user has permissions
> to access all directories A,B,C, and D, but not the "private" directory.
> I then add a path filter in my ListFile to exclude the "private" directory
> (for example: (?!(private)).* )
> When I start the ListFile it errors because the NiFi service user does not
> have permissions to "private" directory even though I have no intention of
> listing anything from that directory. Since it Errors it does not listed
> files from any directory including those which have the needed permissions.
> If I give the NiFi service user access to that "private" dir then the listing
> works ignoring the "private" dir files.
> The processor should skip the files and directories without sufficient
> privileges regardless of the filter. The filter will be applied afterward.
> Users may not have ability to edit permissions on some sub directories. And
> with other sub-directories having being dynamically created or having a very
> large number of sub-directories, creating a separate ListFile for each
> sub-directory is not a desirable solution either.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
