1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
To trigger job_b after job_a completes successfully using Glue workflows:
- Create a Glue workflow with two triggers - one each for job_a and job_b
- The trigger for job_a should have job_a as the target resource
- The trigger for job_b should have job_b as the target resource and job_a as the watched resource
- This will make the trigger for job_b fire only after job_a is completed successfully
- Add both triggers to the Glue workflow
- Start job_a through any method like Lambda. The workflow will take care of automatically starting job_b after job_a is done
You do not need EventBridge for this use case as Glue workflows are designed to handle these dependencies between jobs.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Thanks for your reply. I tried doing this, but did not work. As you have mentioned in the 1st point, I created a trigger with "Trigger Type" as "Job Or Crawler Event" and "Conditional Logic" to "All". The I gave watched and target resource as JOB_A and tried creating it. But the trigger failed to create with error: "error message: Job cannot be a Predicate and Action for Conditional Trigger.". We cannot trigger with watched & target event as same job. Also cannot skip the "Watched Resource" option. Can you please check this? Not sure, If I misunderstood what you told or missing something here?