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

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

Github user ijokarumawak commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/3169#discussion_r232895405
  
    --- Diff: 
nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/src/main/java/org/apache/nifi/processors/orc/PutORC.java
 ---
    @@ -63,7 +65,11 @@
                     + "the path is the directory that contains this ORC file 
on HDFS. For example, this processor can send flow files downstream to 
ReplaceText to set the content "
                     + "to this DDL (plus the LOCATION clause as described), 
then to PutHiveQL processor to create the table if it doesn't exist.")
     })
    -@Restricted("Provides operator the ability to write to any file that NiFi 
has access to in HDFS or the local filesystem.")
    +@Restricted(restrictions = {
    +        @Restriction(
    +                requiredPermission = RequiredPermission.WRITE_FILESYSTEM,
    +                explanation = "Provides operator the ability to delete any 
file that NiFi has access to in HDFS or the local filesystem.")
    --- End diff --
    
    Is the term 'delete' correct?


> PutORC processor "Restricted" still requires access to restricted components 
> regardless of restriction
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-5815
>                 URL: https://issues.apache.org/jira/browse/NIFI-5815
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.6.0, 1.7.0, 1.8.0, 1.7.1
>            Reporter: Matthew Clarke
>            Assignee: Pierre Villard
>            Priority: Major
>
> When the new more granular policies were introduced for the "Access 
> Restricted Components" access policy, the PutORC processor was missed.  It 
> still requires that users have full access to all restricted components in 
> order to use this processor.  This has side affect of any user who needs to 
> use this components having access to all components in every sub policy of 
> restricted-components.



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

Reply via email to