Shubham, I'm sorry, I just found this e-mail in my Junk mail :( Looks like it's been there for quite a long time, so I apologize for not responding sooner!
Did you ever make any headway with this issue? The way that the processor works, it requires a FlowFile as input. It cannot be run as a "Source" Processor. There is a ticket [1] to update the Processor so that it can in fact be used as a Source Processor. In the meantime, you could work around the issue by adding a GenerateFlowFile ahead of it and scheduling it to run every 5 minutes or however often you want the query to run. When the GenerateFlowFile runs, it will then send the FlowFile to ExecuteSQL so that it will perform the query. Does this make sense? Again, sorry for taking so long to get back to you! -Mark [1] https://issues.apache.org/jira/browse/NIFI-932 Date: Tue, 8 Sep 2015 13:44:23 +0530 Subject: Fwd: Facing problem from ExecuteSQL processor From: [email protected] To: [email protected] Hi, Did you get a chance to look into this issue ? Thanks, ---------- Forwarded message ---------- From: Shubham Bansal <[email protected]> Date: 4 September 2015 at 14:03 Subject: Facing problem from ExecuteSQL processor To: [email protected] Hi, I am using ExecuteSQL processor in my flow. Infact , that is the only processor I have added to the flow. I have added DBCPConnectionPool service to this processor. I am attaching screenshots for the configuration done for these. There is no error on the connection side but I am not able to fetch any data. Where exactly will this data go ? Please help me with this. Thanks, -- Shubham Bansal, Software Engineer, 4th Floor, Pioneer Towers, Madhapur, Hyderabad M: +91 9059328793 W: www.whishworks.com -- Shubham Bansal, Software Engineer, 4th Floor, Pioneer Towers, Madhapur, Hyderabad M: +91 9059328793 W: www.whishworks.com The contents of this e-mail are confidential and for the exclusive use of the intended recipient. If you receive this e-mail in error please delete it from your system immediately and notify us either by e-mail or telephone. You should not copy, forward or otherwise disclose the content of the e-mail. The views expressed in this communication may not necessarily be the view held by WHISHWORKS.
