About daniel_kenshalo

daniel_kenshalo · ‎10-27-2017

I'm not sure if this helps but, below is a sample nginx configuration that worked for me. I didn't need the X-ProxyContextPath but t, my requests are still context root of "/nifi". I suspect I'd need the X-ProxyContextPath if my requests were something like, <my-site>/nifi location /nifi { proxy_pass http://<nifi-ip/dns-name>:<nifi-port>/nifi; proxy_set_header 'X-ProxyScheme' 'http'; # proxy_set_header 'X-ProxyHost' '<external-proxy-ip>'; proxy_set_header 'X-ProxyPort' '<proxy-ip>'; }

daniel_kenshalo · ‎10-27-2017

I got HTTP 502 the first time I tried the proxy and then I fixed the iptables. You could try: iptables -I INPUT -j ACCEPT as a test. This opens up everything.

daniel_kenshalo · ‎10-19-2017

Thanks Bryan. Makes sense. I can see why there wouldn't be TRANSFER events. I think that there is a reference to the previous provenance event in all provenance events, so it may be also useful to add a label named edge (or something better) that could hold any arbitrary string. Most of the time it would be success or failure, but the attribute could also hold custom values that developers can use for processor exits. This way consumers could generally know how a flow file arrived at a processor. I don't know the internals of how provenance events work so this also may create overhead or unwanted dependencies, or maybe there is a way to do this with a different reporting task. My use case it to be able to report status to a UI as processors complete/fail.

daniel_kenshalo · ‎10-18-2017

@Bryan Bende Is there a way to determine the state (failed, success) that came into a processor through provenance events? I'm trying to build a status API for a client web application that uses nifi behind the scenes to manage data flows in and out of our system. For example, a user may upload a large file and I want to report back to UI that the file is uploading and then when it is complete or fails (there are many other operations that kick off in this process) I was thinking that I could use the provenance events to track and manage these types of operations and I've successfully setup the Site2Site provenance replication described in this article: https://community.hortonworks.com/articles/72727/extracting-nifi-provenance-data-using-sitetositepr.html so I can propagate the provenance events out to Kafka etc, but I can't figure out how to accomplish my requirement. One way I could think to do this is to a a status attribute to each flow file, but this seems hacky and not very extensible. Is there better way, or am I trying to use provenance for something which they were not intended?

Online	Offline
Last Visited	‎10-28-2017 04:54 AM

Date Registered	‎10-18-2017 11:06 PM
Last Visited	‎10-28-2017 04:54 AM
Total Messages Posted	4
Total Kudos Received	1

Re: Running Apache NiFi behind a proxy

Re: Nifi Nginx Proxy 502 Bad Gateway Error

Re: Nifi provenance events and processor state tra...

Nifi provenance events and processor state transit...