Brajendra, As you have said, even though the documentation for ExecuteSQL mentions, "It is meant to execute SELECT", it ultimately accepts and executes DML commands. Looking at the code, there are no way of restricting it to accept & execute SELECT query only. There is this Jira NIFI-4843 <https://issues.apache.org/jira/browse/NIFI-4843> which mentions something similar. Either we can do one thing: Make ExecuteSQL support two types of operation "SELECT" and "DELETE" and be it exposed as a property and in the code we do the check and perform the execution. Thoughts?
Thanks, Sivaprasanna On Mon, Jun 11, 2018 at 11:43 AM, Brajendra Mishra < brajendra_mis...@persistent.com> wrote: > Hi Team, > > > > We are currently using ExecuteSQL processor in our flow. > > As per the documentation, ExecuteSQL processor should only be worked for > SELECT queries, but it is working for other SQL commands as well for DELETE > and UPDATE queries. > > > > In our current flow implementation we want to restrict user to execute > only SELECT queries. How we can achieve this requirement? > > > > For your reference, here I have attached screen prints of ‘ExecuteSQL’ > processor: > > > > Brajendra Mishra > > Persistent Systems Ltd. > > > DISCLAIMER > ========== > This e-mail may contain privileged and confidential information which is > the property of Persistent Systems Ltd. It is intended only for the use of > the individual or entity to which it is addressed. If you are not the > intended recipient, you are not authorized to read, retain, copy, print, > distribute or use this message. If you have received this communication in > error, please notify the sender and delete all copies of this message. > Persistent Systems Ltd. does not accept any liability for virus infected > mails. >
