Parameterizing the nifi flow

2017-08-11 Thread More, Vikram (CONT)
Hi,



I have a nifi flow which pulls/extracts from source database table and loads 
into target database table. This flow will run several times in a day to get 
delta records from source table (more like batch process running every 3-4 
hrs). Now I need to replicate this same process for 100+ different source 
tables. So rather than creating 100+ nifi flows for each separate table, can I 
create main flow (let's say template) and pass parameter like source extract 
sql, target load sql to main flow. And repeat these steps for each source table 
. Has anyone tried parameterizing the nifi flows, can you please advice . We 
are using NiFi 1.1.0



Appreciate any thoughts here.


Thanks & Regards,
Vikram



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.


RE: ExecuteSQL question: how do I stop long running queries

2017-09-29 Thread More, Vikram (CONT)
Thanks Matt for quick response. We are running simple queries (without any 
joins or sub-query). For use case I am working, we have to get all rows (kind 
of history) from source table as an initial one time fetch and then later do 
incremental fetch . Haven’t tried out QueryDatabaseTable and GenerateTableFetch 
, will check how they work.
Although for some of the source tables, we have to fetch all rows on daily 
basis. ?

Which version of NiFi would work best for RDBMS processors, I’ll check with 
platform folks if we can go version upgrade.

Thanks, Appreciate your help

From: Matt Burgess [mailto:mattyb...@gmail.com]
Sent: Friday, September 29, 2017 6:48 PM
To: users@nifi.apache.org
Subject: Re: ExecuteSQL question: how do I stop long running queries

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<mailto: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.


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.


ExecuteSQL question: how do I stop long running queries

2017-09-29 Thread More, Vikram (CONT)
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.