Member since
07-19-2023
7
Posts
1
Kudos Received
0
Solutions
08-14-2024
04:33 AM
1 Kudo
Hello, @CommanderLaus wrote: Hello everyone, do you happen to know if the GitHub integration of NiFi 2.0.0 M4 also works for GitLab? I think I have entered everything correctly, but I get the error message that my repo does not exist. With "normal" GitHub-API it Works fine! Best regards Simplify the Configuration: Start with a basic configuration and gradually add complexity. Enable Debugging: Use NiFi's logging and debugging features to gather more information about the issue. Consult the NiFi Community: Seek help from the NiFi community forums or mailing lists.
... View more
11-22-2023
12:28 AM
@CommanderLaus: First things first, as I see in your netcat command, you are connecting to port 31510, whereas in your error message it seems that you are going on port 1025. Something is not right here and you need to check your configurations. Try a netscan on port 1025 as well and see if you have any connectivity. And besides netscan try using telnet as well. Next, regarding your DBCP Connection Pool, in the property Database Driver Location(s), I highly recommend you to write the full path to the JAR File and not using "." or any other shortcuts.
... View more
09-13-2023
02:50 AM
Hi @SAMSAL , that's pretty simple, but works fine for me. Thanks for the advice. Regards Maik
... View more
07-21-2023
07:49 AM
Hi @CommanderLaus , If you do anything manually with the processor you are trying to change its Running State through the API, then yes the revision will be updated. In my case what I do is basically the first API InvokeHttp is to get the latest revision using the following GET API: https://localhost:8443/nifi-api/processors/${pipeline.start.processor.id} This will give the following response where you can parse the latest "version" value using something like EvaluateJsonPath processor and store the value in an attribute: {
"revision": {
"clientId": "value",
"version": 0,
"lastModifier": "value"
},
"id": "value",
"uri": "value",
"position": {…},
"permissions": {…},
"bulletins": [{…}],
"disconnectedNodeAcknowledged": true,
"component": {…},
"inputRequirement": "value",
"status": {…},
"operatePermissions": {…}
} Then use extracted version attribute to build the next API post Body , for example in my case I use ReplaceText processor to generate the post body : {
"revision": {
"clientId": "${pipeline.start.processor.id}",
"version": ${processorVersion}
},
"state": "...",
"disconnectedNodeAcknowledged": true
} Hope that helps.
... View more