Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

ExecuteSQL reads data from database an infinite number of times

Solved Go to solution
Highlighted

ExecuteSQL reads data from database an infinite number of times

Explorer

Processor reads data from database an infinite number of times.
How can I limit this so that he reads the data only once and does not repeat?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: ExecuteSQL reads data from database an infinite number of times

Super Guru
@Vladislav Shcherbakov

You can change the schedule of ExecuteSql Processor

Right Click --> Configure --> Scheduling tab

77836-executesql.png

Executesql either trigger based on Timer driven (or) cron driven, as shown in the above RunSchedule 1111111110 sec means the processor trigger once 1111111110 sec. you can use like 1 min,1 hr instead of specifying in sec.

Cron driven use this link to make your cron expression then change the scheduling strategy to cron driven and keep your cron expression in Run Schedule.

ExecuteSql processor doesn't store the state if you want to incrementally pull the data then use either incremental fetch using QueryDatabaseTable (or) Generate Table Fetch processors as these processors stores the state based on max value column provided and pulls only the changes made after the store state.

2 REPLIES 2

Re: ExecuteSQL reads data from database an infinite number of times

Super Guru
@Vladislav Shcherbakov

You can change the schedule of ExecuteSql Processor

Right Click --> Configure --> Scheduling tab

77836-executesql.png

Executesql either trigger based on Timer driven (or) cron driven, as shown in the above RunSchedule 1111111110 sec means the processor trigger once 1111111110 sec. you can use like 1 min,1 hr instead of specifying in sec.

Cron driven use this link to make your cron expression then change the scheduling strategy to cron driven and keep your cron expression in Run Schedule.

ExecuteSql processor doesn't store the state if you want to incrementally pull the data then use either incremental fetch using QueryDatabaseTable (or) Generate Table Fetch processors as these processors stores the state based on max value column provided and pulls only the changes made after the store state.

Re: ExecuteSQL reads data from database an infinite number of times

Explorer

Perfect! Thanks!
I'll try QueryDatabaseTable for it. It'll be better!

Don't have an account?
Coming from Hortonworks? Activate your account here