Re: queued files

Interesting. Thanks for the update and the template. I use osx as a playground, but this will have to be implemented on RHEL. I'll see about downloading or building this and testing. Performance will be critical due to the volume of data; I've run into some python-based detection libraries

Re: queued files

Hello Charlie, I was looking back through and saw this wasn't totally resolved yet. Couple questions. First, what system are you using? There are a couple of options for the stream command depending on what you're using. Also are you able to get new commands (using yum or brew)? The key

Re: queued files

Charlie, The behavior you described usually means that the processor encountered an unexpected error which was thrown back to the framework which rolls back the processing of that flow file and leaves it in the queue, as opposed to an error it expected where it would usually route to a failure

Re: queued files

Charlie, The fact that this is confusing is something we agree should be more clear and we will improve. We're tackling it based on what is mentioned here [1]. [1] https://cwiki.apache.org/confluence/display/NIFI/Interactive+Queue+Management Thanks Joe On Thu, Nov 19, 2015 at 10:30 PM, Corey

queued files

I have a question on troubleshooting a flow. I've built a flow with no exception routing, just trying to process the expected values first. When a file exposes a problem with the logic in my flow, it queues up prior to the flow that is raising the bulletin. In the bulletin, I can see an id, but

Re: queued files

You can also check the NiFi logs for a searchable id or for what the previous processor ID produced to help search provenance. On Nov 19, 2015 21:22, "Bryan Bende" wrote: > Charlie, > > The behavior you described usually means that the processor encountered an > unexpected

Re: queued files

These guys are right. The file to look in for the uuid is the nifi-app.log. Also if you wanted to see what the processor itself was doing, you could right click on the processor, get its uuid and while it is running, run (assuming it is on Linux): tail -F nifi-app.log | grep uuid This will just