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

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

GitHub user mcgilman opened a pull request:

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

    [NIFI-5009] [NIFI-5008]: Addressing restricted component annotations

    NIFI-5009:
    - Fixing required permission for PutParquet.
    
    NIFI-5008:
    - Ensuring all restricted components are tagged as such.

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

    $ git pull https://github.com/mcgilman/nifi NIFI-5009

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

    https://github.com/apache/nifi/pull/2583.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 #2583
    
----
commit 085891e81aaf69040c81f0ad35a804ddaeb11f6e
Author: Matt Gilman <matt.c.gilman@...>
Date:   2018-03-26T13:20:40Z

    NIFI-5009:
    - Fixing required permission for PutParquet.
    
    NIFI-5008:
    - Ensuring all restricted components are tagged as such.

----


> PutParquet processor requires "read filesystem" restricted component 
> permission but should be "write filesystem" permission instead
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-5009
>                 URL: https://issues.apache.org/jira/browse/NIFI-5009
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework, Core UI
>    Affects Versions: 1.6.0
>            Reporter: Andrew Lim
>            Assignee: Matt Gilman
>            Priority: Minor
>         Attachments: PutParquet_permission.jpg
>
>
> Similar to the other Put******* restricted processors, this is a write 
> processor, so it should require "write filesystem" permissions.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to