Skip to content

Bug on creating sensor with duplicate task id #539

@irainia

Description

@irainia

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions