nifi-config | Automatically deploy and configure Template on Nifi | Application Framework library

by hermannpencole Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets(3)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | nifi-config Summary

nifi-config is a Java library typically used in Server, Application Framework, Spring Boot, Jenkin applications. nifi-config has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

Automatically deploy and configure Template on Nifi

Support

Quality

Security

License

Reuse

Support

nifi-config has a low active ecosystem.

It has 49 star(s) with 35 fork(s). There are 13 watchers for this library.

It had no major release in the last 6 months.

There are 10 open issues and 25 have been closed. On average issues are closed in 15 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of nifi-config is current.

Quality

nifi-config has 0 bugs and 0 code smells.

Security

nifi-config has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

nifi-config code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

nifi-config is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

nifi-config releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

nifi-config saves you 1792 person hours of effort in developing the same functionality from scratch.

It has 3962 lines of code, 225 functions and 37 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed nifi-config and discovered the below as its top functions. This is intended to give you an instant insight into nifi-config implemented functionality, and help decide if they suit your requirements.

Main entry point
Find the DTO of the flow
Update connection list
Update the controllers
Stops processor or port
Set the state of port
Set processor state
Runs a runnable
Extract processor DTO from processor
Converts a connection entity to a Connection object
Compares two connection objects

Get all kandi verified functions for this library.

nifi-config Key Features

No Key Features are available at this moment for nifi-config.

nifi-config Examples and Code Snippets

Deploy and configure Template on Nifi,What can I configure ?

Java

Lines of Code : 66

License : Permissive (Apache-2.0)

Copy

{  
  "processors": [
	{
	  "name": "ExecuteSQL",
	  "config": {
		"properties": {
		  "Database Connection Pooling Service": "85f67694-015d-1000-5071-8cd46e8b2e47",
		  "Max Wait Time": "5 seconds",
		  "dbf-normalize": "false",
		  "dbf-user-logica

Deploy and configure Template on Nifi,What can I configure ?,Sample usage

Java

Lines of Code : 41

License : Permissive (Apache-2.0)

Copy

java -jar nifi-deploy-config-1.1.15.jar \
  -nifi http://ip-nifi-dev:8080/nifi-api \
  -branch "root>my group>my subgroup" \
  -conf /tmp/test2.json \
  -mode extractConfig

java -jar nifi-deploy-config-1.1.15.jar \
  -nifi http://ip-nifi-prod:

Deploy and configure Template on Nifi,What can I configure ?,Advanced Options

Java

Lines of Code : 15

License : Permissive (Apache-2.0)

Copy

 -timeout             allows specifying the polling timeout in second (defaut 120 seconds); negative values indicate no timeout
 -interval            allows specifying the polling interval in second (default 2 seconds)

-password            password

Community Discussions

Trending Discussions on nifi-config

How do I configure Apache NiFi nifi.web.proxy.host when running in a Docker container?

Changing configuration in running Kubernetes Pod

QUESTION

How do I configure Apache NiFi nifi.web.proxy.host when running in a Docker container?

Asked 2020-Oct-02 at 15:25

I have started Apache NiFi in a container successfully with the command

...

ANSWER

Answered 2020-Jun-05 at 17:55

The Docker container doesn't expose all the settings you need to modify directly for this use case, so you have a few options (responding to your numbered points).

(General) It looks like you provided configurations for multiple context paths, but not the root path (/). As stated in the documentation, there are many component context paths inside the NiFi application, so when putting it behind a proxy, the root path should be proxied.

Correct, there is no editor in the base Docker image. You can build your own image based on this one (either with an editor or with custom properties/scripts to handle this scenario).
The documentation you linked to is discussing granting permission to an external proxy to relay requests. You can add the identity of the proxy as a user in NiFi to grant it permissions through the UI. This is separate from identifying the proxy service to the NiFi application (the nifi.properties settings). There is no way to configure those two settings you listed through the UI.
The current Docker start.sh file lists the environment variables accepted by the Docker image at this time. To add more, please submit a PR or open a Jira requesting an improvement.

Koji Kawamura has provided example configuration and documentation for NiFi running behind a reverse proxy that you may be interested in.

Source https://stackoverflow.com/questions/62218588

QUESTION

Changing configuration in running Kubernetes Pod

Asked 2018-Aug-14 at 11:43

I have written the nifi.properties into a Kubernetes ConfigMap. When I deploy NiFi (as a StatefulSet) I want to have this nifi.properties file to be used by the NiFi I just deployed. To do so I added a volume for the ConfigMap and mounted it in the Container. The associated statefulset.yaml looks like this:

...

ANSWER

Answered 2018-Aug-11 at 19:56

There are two problems with the above setup:

You have to specify the subpath to tell which item you mount from the configmap as a single file, see: https://github.com/kubernetes/kubernetes/issues/44815#issuecomment-297077509
You cannot mount a configmap item as a readwrite volume by default on 1.9.6 and above, so the start script won't be able to replace properties in it, see: https://github.com/kubernetes/kubernetes/issues/62099#issuecomment-378809922

To workaround the second issue you can simply mount the configmap item as a separate file (nifi.properties.tmp) and copy it to the destination by wrapping the container entry point with a custom command.

Source https://stackoverflow.com/questions/51786114

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install nifi-config

You can download it from GitHub, Maven.
You can use nifi-config like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the nifi-config component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: