Member since
07-22-2016
28
Posts
5
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
8238 | 10-26-2018 01:03 AM | |
7135 | 11-08-2017 01:05 AM | |
2733 | 11-02-2017 10:44 PM |
10-26-2018
01:03 AM
Hi, I had the same issue and after i created the SSLContextService, i had to change the property in the InvokeHttp "Always Output Response" to true and this will give you an output, in the output look for the invokehttp.remote.dn, since is a 403 error "Forbidden" it means that the dn does not have access to make this request but your SSLContextService is working. Next step is to add the Identity that will make the https request(invokehttp.remote.dn) in NiFi User UI and run again the InvokeHTTP. Hope this helps
... View more
06-12-2018
11:52 PM
Can you post you json file content ? Test your json path definition at http://jsonpath.com/? , is easy and debug any issues with the json format.
... View more
02-01-2018
09:50 PM
Are you able to ping the S3 or access the S3 endpoint from you NiFi server ? If your NiFi server is on private subnet with no EIP attached you need to create an VPC endpoint to your S3 service If this you case follow this link :https://aws.amazon.com/blogs/aws/new-vpc-endpoint-for-amazon-s3/
... View more
11-23-2017
06:04 AM
Just my Two Cents on it, If you are experiencing a lot of queued flow-files and you want to clear them without having to reload the config.yml, a very quick and dirty way would be to clear all the repos on the minifi edge. Here how i do it - assuming your minifi sits in /opt - you will lose all queued data by doing this, but you no longer have queues.(not ideal) -- before cleanup
/opt/minifi/bin/minifi.sh flowStatus connection:all:health,stats | tail -2 | head -1| jq '.'
/opt/minifi/bin/minifi.sh stop
rm -rf /opt/minifi/flowfile_repository/*
rm -rf /opt/minifi/content_repository/*
rm -rf /opt/minifi/provenance_repository/*
/opt/minifi/bin/minifi.sh start
-- after cleanup
/opt/minifi/bin/minifi.sh flowStatus connection:all:health,stats | tail -2 | head -1| jq '.'
Ideal solution: Use the minifi.sh flowStatus cmd to push data into the NiFi server and monitor this types of stuff. From here you can develop nifi flows to act on what needs to be done to those edge minifi. you can even build a dashboard from this data and actually see how to edges are doing. No doubt Horton has this on the to do list.
... View more
11-09-2017
12:39 AM
yeah i know is not very intuitive 🙂
... View more
11-08-2017
01:05 AM
1 Kudo
Hi, You almost got it right 🙂 In the Replacement Value: type "Shift-Enter" -- this will add a new line as replacement value. the search value will remove all empty lines and prefix spaces. Also i have attached a sample template : replace.xml
... View more
11-07-2017
10:16 PM
Thanks @Hellmar Becker
... View more
11-05-2017
11:15 PM
Hi, Very interesting article. In what day to day scenario would this be useful ? Thx
... View more
11-02-2017
10:44 PM
1 Kudo
Hi, Use This - this lists the resources in the server and formats the templates ids into a api call. note: jq -- formats the output to be readable curl -v -X GET http://NiFiServerIP:Port/nifi-api/resources | jq '.' | grep '"/templates/' | awk '{print $2}' | sed 's/\"//g'| sed 's/\/templates//g' | awk '{print "curl -v -X GET http://NiFiServerIP:Port/nifi-api/templates"$1"/download"}' The output should be a Rest Api call: curl -v -X GET http://NiFiServerIP:Port/nifi-api/templates/885dc02e-cb13-429c-bdvd-9a4e0cbe1212b/download In the future if you don`t see how is done in the docs you can always SPY on the nifi-app.log, it gives you what you need to know. Hope this helped.
... View more
11-02-2017
10:27 PM
1 Kudo
Use port 587 - it work for me. See link here: https://support.google.com/a/answer/176600?hl=en Note: Before you start the configuration, make sure that Less secure apps is enabled for the desired account.
... View more