Migrating Kylo and NiFi extensions

If custom NiFi or Kylo plugins/extensions have been built, they must copied to all instances of NiFi and Kylo where you wish to use them. Custom NiFi extensions are packaged in .nar format, and must be place in NiFi’s lib directory. With a default Kylo installation, this directory is /opt/nifi/current/lib. Place all custom .nar files there, and restart the NiFi service.

Custom Kylo plugins belong in the /opt/thinkbig/thinkbig-services/plugin directory in a default Kylo installation. Place the .jar files for custom plugins in this directory and manually start and stop the thinkbig-services service.

Operational Considerations

When considering promoting Kylo/NiFi metatdata you will need to restart Kylo:

• Upon changing/adding any new NiFi processors/services (changing code that creates a new Nifi plugin .nar file) you will need to bounce NiFi
• Upon changing/adding any new Kylo plugin/extension (changing the java jar) you will need to bounce Kylo (thinkbig-services)