You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2019/03/21 18:48:00 UTC

[jira] [Commented] (NIFI-6138) NarAutoLoaderTask: NARs are not unpacked after REdeploy

    [ https://issues.apache.org/jira/browse/NIFI-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798333#comment-16798333 ] 

Bryan Bende commented on NIFI-6138:
-----------------------------------

Hi [~aleksi75] , the functionality you described is actually expected behavior...

Loading NARs is currently based on the unique coordinate of the NAR which is the group-artifact-version found in the MANIFEST of the NAR, which typically comes from the Maven coordinates.

We can't load another NAR with same coordinates because it would require cleanly unloading all the classes from the previous NAR with the same coordinates, its the same reason we don't have a way to take NARs out of the application while it is running.

I can see the desire to use this during a dev lifecycle, but it was more geared towards deploying to production without downtime. For development, the only thing I can think of would be to somehow add a timestamp to the version that is produced which typically defaults to project.version with Maven. I haven't played around to see if there is an easy way to do this.

> NarAutoLoaderTask: NARs are not unpacked after REdeploy
> -------------------------------------------------------
>
>                 Key: NIFI-6138
>                 URL: https://issues.apache.org/jira/browse/NIFI-6138
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.9.0
>            Reporter: Alexander T
>            Priority: Minor
>
> Since NiFi 1.9.0 live/auto reloading for nars is implemented by placing them
> in $NIFI_HOME/extensions directory. This works fine in case of first deployment,
> but in case of development you propably have to redelpoy the 'same' NAR multiple times.
> (NAR has same name, but different Timestamp).
> When doing so, NarAutoLoader recognizes a new bundle but does not unpack it (see log)
> {code:java}
> 2019-03-21 09:13:27,740 INFO [NAR Auto-Loader] org.apache.nifi.nar.NarAutoLoaderTask Found ./extensions/nifi-sample-nar-0.1.0-SNAPSHOT.nar in auto-load directory
> 2019-03-21 09:13:27,741 INFO [NAR Auto-Loader] org.apache.nifi.nar.StandardNarLoader Starting load process for 1 NARs...
> 2019-03-21 09:13:27,745 WARN [NAR Auto-Loader] org.apache.nifi.nar.StandardNarLoader Found existing bundle with coordinate at.rsg.ptdpaa.nifi:nifi-sample-nar:0.1.0-SNAPSHOT, will not load /opt/local/nifi/nifi-1.9.1/./extensions/nifi-sample-nar-0.1.0-SNAPSHOT.nar
> 2019-03-21 09:13:27,745 INFO [NAR Auto-Loader] org.apache.nifi.nar.StandardNarLoader No NARs were unpacked, nothing to do{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)