You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "scottp (JIRA)" <ji...@apache.org> on 2018/07/25 14:41:00 UTC
[jira] [Resolved] (MINIFI-466) Failure to correctly use certain
processors not supported out of the box
[ https://issues.apache.org/jira/browse/MINIFI-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
scottp resolved MINIFI-466.
---------------------------
Resolution: Not A Problem
Problem caused by unmet dependencies in the form of the NiFi standad NAR. Suggest some clear location for processor dependencies in MiNiFi? This may already exist and I just failed to find it!
> 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)