Member since
11-30-2017
44
Posts
6
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1406 | 04-16-2018 07:49 PM | |
1714 | 01-05-2018 02:31 PM |
08-23-2018
05:44 PM
This worked, thanks!
... View more
08-21-2018
07:59 PM
I am wanting to delete a process group from NiFi by using a curl command to the API. I tried using the following command. curl -k -X DELETE -H "Authorization: Bearer $token" $cluster_url/nifi-api/process-groups/$process_group_uuid But I get the error that the revision must be specified. When I delete a process group using the UI, I can see using Chrome dev tools that both a revision and client ID are specified. How can I get these values so I can use curl to delete the process group?
... View more
Labels:
- Labels:
-
Apache NiFi
07-31-2018
01:02 PM
@Pierre Villard This works for me if I leave out the `clientID` part as NiFi will generate it's own, but I have a use case where I would like to provide my own UUID. Is this possible? I tried using `uuidgen` to get a UUID in bash but the POST then fails.
... View more
07-31-2018
12:40 PM
I am writing a script that will dynamically create a process group with a given name based on user input. I then am wanting to deploy a template inside of this process group immediately after it gets created. Since NiFi generates the UUID for the new process group after the POST to the API, I am stumped on how to get the UUID of the newly created process group. How can I accomplish this so I can then deploy a template inside of it?
I tried generating a UUID myself for the process group in bash by using `uuidgen` so I could easily track this in a variable, however the POST fails for some reason when I send this along with the name.
Here is the curl that is failing when I provide a uuid I generated. curl -k -X POST -v -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' -d '{"revision":{"clientID":"'$uuid'","version":0},"component":{"name":"'$CLUSTER_NAME' '$FLOW_NAME'"}}' https://myhost.com:9091/nifi-api/process-groups/$EXISTING_PROCESS_GROUP/process-groups/ If I remove the `clientID` part of the JSON, the POST works and NiFi generates a UUID for me, which results in my original problem.
... View more
Labels:
- Labels:
-
Apache NiFi
07-23-2018
06:41 PM
@sbabu Getting the token this way does not work for me as there is a '%' in the password I am using, which causes curl to throw an error. How can I get around this? The script I am developing is going to be used by different people so I cannot know ahead of time to escape any special characters.
... View more
06-25-2018
05:54 PM
@Aakash Singh Did you find out how to do this on a kerberized cluster?
... View more
06-25-2018
01:09 PM
@Smart Solutions
Were you able to get an answer for this?
... View more
05-07-2018
01:20 PM
@Matt Burgess Thanks for opening the JIRA Matt. As a workaround in the meantime, I discovered I can use ${s2s.host} to get the host name, I just then need to use an UpdateAttribute processor to add this as an actual property to the flowfile.
... View more
05-04-2018
01:09 PM
@Matt Burgess This would be better as it would be easier to map the hostname but still not a perfect solution. Also, I didn't see this as a field in the bulletin's JSON. I'm currently running HDF 3.0.1 (NiFi 1.2) so I'm assuming it's not in my version?
... View more
05-03-2018
07:47 PM
I am developing a flow where I need the hostname of where a bulletin is coming from. Currently, a large portion of my flow is getting this by me first manually determining what hostname is associated with which bulletinNodeId, and then using the RouteOnAttribute processor to map this to the actual hostname. This isn't going to be scalable if I need to first manually determine which bulletinNodeId is associated with which hostname. Is there a better way to go about getting this hostname?
... View more
Labels:
- Labels:
-
Apache NiFi