Skip to content

A way to propagate warning generated from a DAG file to DagWarning #37699

Open
Open
A way to propagate warning generated from a DAG file to DagWarning#37699
Labels
area:dag-processorarea:data-aware-schedulingassets, datasets, AIP-48, AIP-76, AIP-74, Asset Partitionspriority:lowBug with a simple workaround that would not block a release

Description

@uranusjr
uranusjr
opened on Feb 26, 2024

Body

From #37005 (comment)

This should automatically cover #29275, I think.

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Activity

  1. uranusjr
    added
    area:datasets
    area:dag-processor
    on Feb 26, 2024

  2. uranusjr commented on Feb 27, 2024

    @uranusjr
    uranusjr
    on Feb 27, 2024
    MemberAuthor

    Err, this is more awkward than I anticipated since DAG warnings are tied to a DAG, not a file like ImportError. Talking about having foresight when designing things…

  3. eladkal
    added
    area:data-aware-schedulingassets, datasets, AIP-48, AIP-76, AIP-74, Asset Partitions
    and removed
    area:datasets
    on Mar 25, 2025
  4. uranusjr
    added
    priority:lowBug with a simple workaround that would not block a release
    on Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:dag-processorarea:data-aware-schedulingassets, datasets, AIP-48, AIP-76, AIP-74, Asset Partitionspriority:lowBug with a simple workaround that would not block a release

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions