Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/1372
Just some initial thoughts on the convo thus far:
From a release perspective, I don't think we should be maintaining
versioned directories. Along the lines of what @JPercivall was mentioning,
the code in here should coincide with the current release we have. When things
are voted upon and released we can have a corresponding image. This would make
things a bit tricky in the interim given that it's looking for a specific
location. Not sure how those logistics would work out exactly, but short of
having a separate repo and vote process, may be something that we need to work
against.
There is nothing that precludes volumes being specified at container
instantiation. It would be nice to have them as defaults, but is not
explicitly required.
Custom processors would make sense to have an additional volume and update
the config to provide one or more additional lib directories for custom NARs.
These do not necessarily need to be in the lib directory, and from a
maintainability standpoint, would be nice to have a dedicated location for
these custom NARs.
---
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.
---
