subject:"ExecuteSQL processor running in duplicate\?"

RE: ExecuteSQL processor running in duplicate?

2016-09-14 Thread Crystal Deschamps Fogdall (cdeschampsfo)

Thanks for all of your help Lee! From: Lee Laim [mailto:lee.l...@gmail.com] Sent: Tuesday, September 13, 2016 13:08 PM To: users@nifi.apache.org Subject: Re: ExecuteSQL processor running in duplicate? Hi Crystal, While this may not be the root cause of your specific case, I suspect the

Re: ExecuteSQL processor running in duplicate?

2016-09-13 Thread Lee Laim

Hi Crystal, While this may not be the root cause of your specific case, I suspect the sequence of: ->stopping the processor, ->changing concurrent task setting, ->then starting the timer driven processor generated the rogue flowfile in the queue. Timer driven processors are triggered on start,

ExecuteSQL processor running in duplicate?

2016-09-12 Thread Crystal Deschamps Fogdall (cdeschampsfo)

I'm using NiFi for a very simple, yet non-standard way - as a POC scheduler to call an existing stored procedure using an ExecuteSQL processor. The processor is timer driven (every 4 hours), uses a basic JDBC connection, and executes a stored procedure call that contains one hard-coded variable.