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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
