Ability to include additional libraries in the Nifi containers
See original GitHub issueDatabase processors need database drivers libraries in the Nifi containers.
The current hack is:
wget https://jdbc.postgresql.org/download/postgresql-42.2.6.jar
kubectl cp ./postgresql-42.2.6.jar fadi/fadi-nifi-0:/opt/nifi/postgresql-42.2.6.jar
rm postgresql-42.2.6.jar
It would be nice to be able to specify a list of libraries that would be downloaded and put in nifi_home/lib
as an additional option.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
NiFi System Administrator's Guide - Apache NiFi
User1 can add components to the dataflow and is able to move, edit and connect all ... NOTE: Additional library directories can be...
Read more >Adding additional python modules in NiFi Container
If you want to use native libraries, use ExecuteStreamCommand to invoke the python runtime via the command line, external of the NiFi JVM....
Read more >Apache NiFi - Class Loading
Some components (processors, controller services, reporting tasks) may need to load additional libraries provided by the user at runtime.
Read more >Maven config. for custom processor to Read/Write HDFS files
Try replacing the NAR POM dependency on nifi-standard-services-api-nar to nifi-hadoop-libraries-nar, this should provide all the classes/JARs/ ...
Read more >nifi 0.4.3 · helm/cetic - Artifact Hub
You'll be able to contact the NodePort service, from outside the cluster, ... postStart, Include additional libraries in the Nifi containers by using...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I propose to use a postStart as explained here: https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/
We will have something like:
If you have a better idea, don’t hesitate.
@terence-bigtt yes, we could have an extra volumeMount to give the possibility to create other volume mounts , something like this:
for the values.yaml