[jira] [Commented] (NIFI-2919) NiFi GetFile processor silently refuses to work if write permission is not given to the input directory

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on NIFI-2919:
--------------------------------------

GitHub user olegz opened a pull request:

    https://github.com/apache/nifi/pull/1147

    NIFI-2919 improved GetFile to fail if target directory is inaccessible

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/olegz/nifi NIFI-2919

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1147.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1147
    
----
commit e755cbddad5bd5acd4be1a5cbf1ea109f4125897
Author: Oleg Zhurakousky <ol...@suitcase.io>
Date:   2016-10-19T13:30:12Z

    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)