I am looking for guidance on an issue I am facing concerning utilizing the autoloading of custom processors using the extensions directory.
The issue is with autoloading custom processor NARs and being able to see them in the UI without a restart of the docker container. I can confirm that the NARs are showing up in the extensions folder as they should but while tailing the docker logs to see the if the autoloader is picking it up it is not.
If anyone has any tips on troubleshooting this I would be very grateful!
Data Engineer, Architecture
S&P Global | Market Intelligence
East Coast, USA (Remote)
~~~ *~*~ Happy Data Flowing ~*~* ~~~
The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.
I confirmed previously that autoload applies to an initial load and won't hot-reload on NAR update (instead requires an instance restart).
If the custom component doesn't come up, I'm pretty sure there was a problem with dependency resolution. Check the startup logs for errors and any WARN messages from the nifi module loader, it should tell more.
Hope this helps,
Very important to distinguish here...
You cannot hot reload the same nar (same component version info in the manifest). However, you can hot load additional new versions and select them in the UI. If you're tossing a new copy of the nar with the same manifest metadata in the lib it wont see it until restart. But if you tweak the metadata of the nar it should.
On Thu, May 28, 2020 at 2:16 PM Andrew Grande <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|