[
https://issues.apache.org/jira/browse/NIFI-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070629#comment-16070629
]
ASF GitHub Bot commented on NIFI-4135:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/1956
This looks good! Made sure existing config can run without the new
classpath element, and then verified I could start the Ranger authorizer with
it.
My only comment, and I know this is super picky, but can we switch the
order of `class` and `classpath` in the XSD so that it would be identifier,
class, classpath?
I think it just reads a little cleaner to know which authorizer we are
talking about before reading the classpath.
> RangerNiFiAuthorizer should support storing audit info to HDFS
> --------------------------------------------------------------
>
> Key: NIFI-4135
> URL: https://issues.apache.org/jira/browse/NIFI-4135
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: Yolanda M. Davis
> Assignee: Yolanda M. Davis
>
> When using Ranger to support authorization an option to log auditing
> information to HDFS can be supported. The RangerNiFiAuthorizer should be
> prepared to communicate with a hadoop cluster in order to support this
> feature. In it's current implementation the authorizer does not have the
> hadoop-client jars available as a dependency nor does it support the ability
> to refer to the required *.site.xml files in order to communicate without
> using the default configuration. Both of these changes are needed in order
> to send audit info to HDFS.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
