Tyler, The ExecuteSQL Processor expects to have incoming connections and will only run if it has an incoming FlowFile. I.e., it cannot be used as a "Source Processor." There is a ticket [1] to allow it to be the first Processor in the flow, but right now it will not run unless it has input.
One way to work around this problem in the mean time is to instead use a GenerateFlowFile processor that is scheduled to run every 5 minutes instead. Then connect the GenerateFlowFile processor to ExecuteSQL. This way, the ExecuteSQL processor will receive input so that it runs every 5 minutes. Please let me know if this will work for you! Thanks -Mark [1] https://issues.apache.org/jira/browse/NIFI-932 ________________________________ > From: [email protected] > Date: Sun, 13 Sep 2015 23:00:18 -0600 > Subject: Help with ExecuteSQL > To: [email protected] > > I'm trying to push data from SQLServer to HDFS. I've successfully > enabled a DBCPConnectionPool (it only enables if it can connect. I've > checked this several different ways). I've set it to run a query on a > cron and a timer and it always shows that it's running, but isn't > returning any rows. I've changed the query to be something that always > returns a single row and even then it shows zero rows coming back but > the number of tasks over the last 5 minutes run is exactly what it > should be. The down stream components are stopped so I can see if the > queues are filling up and they sit at 0. > > I'm happy to provide any more information that's required. Any ideas on > what might be going on or how to see any logs of errors that might be > silently happening?
