[
https://issues.apache.org/jira/browse/NIFI-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635802#comment-16635802
]
ASF GitHub Bot commented on NIFI-5648:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/3040
@kemixkoo I can understand where the desire for this comes from but I think
this is a dangerous approach. Fundamentally we're saying that we know at
startup time there is a classpath issue. Continuing to startup as if it
appears ok despite knowing that and without a more holistic approach leads to a
poor user experience. Instead of this change I think we should focus on adding
an extension registry api to the Flow Registry project. There we can have nars
live and NiFi instances can source them at runtime. Issues with those nars are
then well managed/clear and don't affect a live instance. It also means
instances dont require restart to source new versions/etc..
> If one Processor or Controller Service load failure, will block to launch
> -------------------------------------------------------------------------
>
> Key: NIFI-5648
> URL: https://issues.apache.org/jira/browse/NIFI-5648
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Extensions
> Affects Versions: 1.7.1
> Reporter: Kemix Koo
> Priority: Major
>
> If one Processor or Controller Service load failure, will block NiFi to
> launch totally.
> I think, should ignore the error one and log it, won't block at all.
> for example, the processor or controller service missed the dependencies,
> because the jar license. when use, need provide the jars in lib path or jdk
> classpath manually, and relaunch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
