[ https://issues.apache.org/jira/browse/MINIFI-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555774#comment-16555774 ]
Aldrin Piri commented on MINIFI-466: ------------------------------------ [~scottp] okay thanks. Yeah, unfortunately some NARs can have some additional dependencies which I hope the logs should highlight if that is the case. Unfortunately, this can be a bit problematic for what is a manual process and not great transparency in terms of what those items are. Regardless, will keep an eye on this issue and we can see how to improve. Thanks! > Failure to correctly use certain processors not supported out of the box > ------------------------------------------------------------------------ > > Key: MINIFI-466 > URL: https://issues.apache.org/jira/browse/MINIFI-466 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Agent Configuration/Installation > Affects Versions: 0.5.0 > Environment: Windows (Server 2008 r2 onwards) > Reporter: scottp > Assignee: Aldrin Piri > Priority: Minor > > On adding the correct NAR file to the lib directory for windows event log > processors, MiNiFi proceeds to still fail to intialise the processor, > creating a ghost processor in the logs. A workaround solution has been found > for this: > # Copy in the NAR file to the lib directory as instructed. > # Run MiNiFi and allow to fail to intialise the processor for a suitable > flow. > # Stop MiNiFi. > # Copy unpacked jar files from > $MINIFI_HOME/work/nar/extensions/nifi-windows-event...[etc.]/META-INF/bundled-dependencies/. > # Paste in lib directory of MiNiFi. > # Run MiNiFi, processors should now initialise correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)