You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug happens when we want to create one or more sensors that already exist. So far, this bug happens when we encounter the following scenario:
duplicate job name being used as sensor
let's say we have job1 exists in project1 and project2
at the same time, we have job2 that requires job1 to run first
during job2 dag compilation, it will encounter job1 twice as the dependency, when creating the sensor
two or more hooks with the same type
let's say we have job1 with two same hooks, for example, let's name the hooks bq2bq
during job1 dag compilation, it will encounter hook_bq2bq twice, and this causes error
Expected behavior
For this issue, we need to come up with a way to ensure the task_id is unique. And along with that, the duplication shouldn't happen and no error is encountered.
The text was updated successfully, but these errors were encountered:
Describe the bug
This bug happens when we want to create one or more sensors that already exist. So far, this bug happens when we encounter the following scenario:
job1
exists inproject1
andproject2
job2
that requiresjob1
to run firstjob2
dag compilation, it will encounterjob1
twice as the dependency, when creating the sensorjob1
with two same hooks, for example, let's name the hooksbq2bq
job1
dag compilation, it will encounterhook_bq2bq
twice, and this causes errorExpected behavior
For this issue, we need to come up with a way to ensure the
task_id
is unique. And along with that, the duplication shouldn't happen and no error is encountered.The text was updated successfully, but these errors were encountered: