How to configure and control ETL Schedule Frequency
EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-02-1112:23 PM
How to configure and control ETL Schedule Frequency
Good day all!
A bit of background first... as most know, ITA offers an ETL process for exposing modeled data via PostgreSQL DB's. When setting up an ETL job, there's options for setting the "Schedule Frequency" to be an interval. The available option is to set an interval by minute or hours.
This is great, and working well for us... but have run into an issue. Say you have an export DB and and import DB configured on a 3 hour interval. For us, we want to make sure the export job runs first... followed by the import job. Reason for this, we process data outside of ITA using the export... which then feeds into our import job.
The question is : Is it possible to manipulate when these 3 hour intervals fire... without having to destroy the ETL configuration, etc. Last I heard... to only way to kick these job into gear in the proper order... it's about when you CREATED the ETL job originally.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-02-1410:35 AM
Hello Wes, We will check into this in more detail.
My first instinct is to wonder whether this could be done in a "batch" mode where you turn both off from a schedule standpoint, use an external entity to enable the import job and run it "immediately", then wait for that job to complete, then enable and run the export job.
Then turn both off.
Perhaps dev will have a better idea about making the jobs more "dependant" on each other.