Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force an ETL Job to Run #106

Closed
carnalim opened this issue Apr 4, 2016 · 1 comment
Closed

Force an ETL Job to Run #106

carnalim opened this issue Apr 4, 2016 · 1 comment

Comments

@carnalim
Copy link

carnalim commented Apr 4, 2016

Do you guys have any API or way to force a job to run? The only thing I can see is to update the cron_expr but that may cause the job to kick off to many times for testing. I just want to force it to run independently of the cron job.

@SunZhaonan
Copy link
Contributor

Each job can run independently. If you want to run one job to test, follow the instruction here: https://github.com/linkedin/WhereHows/wiki/Coding-Guidelines#testing

If you want to trigger though the backend service, you can manually set the next_run in wh_etl_job table to a small value, disable all other jobs and only enable this one, then restart the service, it will only run this job.

@carnalim carnalim closed this as completed Apr 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants