[
https://issues.apache.org/jira/browse/NIFIREG-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217057#comment-16217057
]
ASF GitHub Bot commented on NIFIREG-43:
---------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/27
NIFIREG-43 Provide configurable extension directories with class load…
…er isolation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry NIFIREG-43
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/27.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #27
----
commit b9c7173b3b27bfd698644b0c9e2134020f68815c
Author: Bryan Bende <[email protected]>
Date: 2017-10-23T20:08:49Z
NIFIREG-43 Provide configurable extension directories with class loader
isolation
----
> Provide configurable extension directories
> ------------------------------------------
>
> Key: NIFIREG-43
> URL: https://issues.apache.org/jira/browse/NIFIREG-43
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 0.0.1
>
>
> We should provide a way to specify directories through
> nifi-registry.properties, where each directory can contain all the JARs for a
> given extension, such as an alternative flow persistence provider. This way
> we can at least provider class loader isolation for each custom directory,
> rather than adding everything to the lib directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
