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

Bug on creating sensor with duplicate task id #539

Open
irainia opened this issue Aug 26, 2022 · 0 comments
Open

Bug on creating sensor with duplicate task id #539

irainia opened this issue Aug 26, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@irainia
Copy link
Member

irainia commented Aug 26, 2022

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:

  • 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.

@irainia irainia added the bug Something isn't working label Aug 26, 2022
@irainia irainia added this to the Reliability - 2022 H2 milestone Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant