Thank you Bryan and Juan Pablo for the quick and very helpful answers!

I'm looking forward to the future changes regarding the seamless
integration of NAR-files in the NiFi registry with NiFi.

Until then I'll stick to my current artifact repository and deployment
pipeline.

Thanks once more!
Have a nice week. :)

Bryan Bende <[email protected]> schrieb am Mo., 20. Juli 2020, 21:21:

> Correct, there is currently not auto-unloading.
>
> On Mon, Jul 20, 2020 at 3:18 PM Juan Pablo Gardella <
> [email protected]> wrote:
>
>> Be aware that using auto-load works for adding only. If you remove it
>> from that directory, it does not remove or update AFAIK, at least, on nifi
>> 1.5.0
>>
>> On Mon, 20 Jul 2020 at 16:10, Bryan Bende <[email protected]> wrote:
>>
>>> Hello,
>>>
>>> The plan is to eventually build a seamless experience on the NiFi side
>>> where it would obtain the required NARs for a versioned flow, but that work
>>> has taken place yet.
>>>
>>> The ability to store the bundles in registry with an API for retrieving
>>> them is the starting point for that.
>>>
>>> Currently there are some NiFi CLI commands which may be helpful for you,
>>> there is one for "download-bundle" [1].
>>>
>>> Also, you don't have to restart nifi, you can put the NAR into the
>>> directory specified by nifi.nar.library.autoload.directory and it will
>>> auto-load, the default directory is ./extensions.
>>>
>>> You need to do a hard refresh of the UI before you'll see the components
>>> since the UI currently caches the list on first load.
>>>
>>> Thanks,
>>>
>>> Bryan
>>>
>>> [1]
>>> https://github.com/apache/nifi/blob/main/nifi-toolkit/nifi-toolkit-cli/src/main/java/org/apache/nifi/toolkit/cli/impl/command/registry/extension/DownloadBundle.java
>>>
>>>
>>>
>>> On Mon, Jul 20, 2020 at 2:24 PM Firlefanz Development <
>>> [email protected]> wrote:
>>>
>>>> Hello,
>>>>
>>>> I recently read about the possibility to upload NAR-files directly into
>>>> the NiFi Registry using its REST api. [1]
>>>> Until now I provide my custom processors by placing the corresponding
>>>> NAR-file onto every node of my NiFi cluster and restart the whole cluster
>>>> as described in the NiFi guides.
>>>>
>>>> I was hoping by providing the NAR-file to the registry those processors
>>>> would be available to the Flow but could make it work.
>>>> Is this possible as of now or planned for the future? When there is no
>>>> direct integration possible with the NiFi cluster, what is the benefit of
>>>> uploading the NAR-file to the registry?
>>>>
>>>> I would love to simplify my build setup, so I'm grateful for any
>>>> guidance on how to achieve that. If possible I'd like to avoid the
>>>> semi-manual task of providing the NAR-file to every cluster node as well as
>>>> the need to restart NiFi.
>>>>
>>>> Thank you in advance!
>>>>
>>>> [1]
>>>> https://nifi.apache.org/docs/nifi-registry-docs/html/user-guide.html#manage-bundles
>>>>
>>>>
>>>>

Reply via email to