Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1635
I think the proposed solution will offer clear, concise rules for when
resources are cloned. It also offers further granularity has it puts the
cloning of the parent resources in control of the extension. The only downside
is that when specified the entire ancestry will be cloned until a referenced
service API is encountered. However, this downside is outweighed by the
benefits of component-based cloning when the flag was previously specified on
the entire parent nar and would affect all descendent components that required
instance classloading even if they didn't actually need it.
---
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.
---
