[
https://issues.apache.org/jira/browse/NIFI-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589854#comment-15589854
]
ASF subversion and git services commented on NIFI-2919:
-------------------------------------------------------
Commit 611cadd231309126a0a7737391f6e07730bb3864 in nifi's branch
refs/heads/master from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=611cadd ]
NIFI-2919 Improved GetFile processor to fail (and provide bulletins) if target
directory is inaccessible.
This closes #1147.
Signed-off-by: Andy LoPresto <[email protected]>
Fixed typos in error messages, renamed variables in test, and cleaned up
unnecessary imports. (+1 squashed commit)
Squashed commits:
[e755cbd] NIFI-2919 improved GetFile to fail if target directory is inaccessible
> NiFi GetFile processor silently refuses to work if write permission is not
> given to the input directory
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2919
> URL: https://issues.apache.org/jira/browse/NIFI-2919
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Fix For: 1.1.0
>
>
> GetFile processor requires write permission to its input directory.
> For example, if nifi is started by a user named 'nifi' (which is the case in
> Ambari environment), and if the input directory does not give write
> permission to user 'nifi', the processor simply stop working without giving
> warning or error messages. From the end user's perspective, it is confusing.
> I'd like to improve the user's experience by providing some check and
> warning. It is similar to the check of the existence of the input directory.
> If the input directory is not present, GetFile already gives error messages
> to the user. The same check can be done for directory permission.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
