Vikram, I'm not at my computer right now so I'm shooting from the hip, but depending on how complex your query is (meaning if it is very simple), take a look at QueryDatabaseTable and GenerateTableFetch, if you are looking to get all rows (versus incremental fetching), you can omit the maximum value column and they act very much like ExecuteSQL. Having said that, even if these are a better choice for your use case, I highly recommend upgrading your NiFi version if possible, as there have been many improvements to all the RDBMS processors in order to help handle use cases like yours.
Regards, Matt > On Sep 29, 2017, at 6:31 PM, More, Vikram (CONT) <vikram.m...@capitalone.com> > wrote: > > Hi , > > I am using ExecuteSQL processor to pull from operational database and for > some of the tables it keeps running for more than 24 hrs, > > 1] During a long-running query from a database (e.g. Oracle) being execute by > an 'ExecuteSql' process, is there a way to check the progress - say by seeing > files, row counts, or whatever? We have some queries that take a while and > can't tell if a process is a success until it succeeds. > > 2] Even after I stop the ExecuteSQL processor, it still continues to run. I > have to stop and restart nifi service to kill/terminate the query session or > follow-up the dba’s to kill the session from user I am querying. Can I find > the session in nifi and terminate it? > > I am using NiFi version – 1.1.0 , any suggestion would be appreciated > > Thanks & Regards, > Vikram More > > > The information contained in this e-mail is confidential and/or proprietary > to Capital One and/or its affiliates and may only be used solely in > performance of work or services for Capital One. The information transmitted > herewith is intended only for use by the individual or entity to which it is > addressed. If the reader of this message is not the intended recipient, you > are hereby notified that any review, retransmission, dissemination, > distribution, copying or other use of, or taking of any action in reliance > upon this information is strictly prohibited. If you have received this > communication in error, please contact the sender and delete the material > from your computer.
