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
It seems like this bug has been reported in the past as well: #5583
Expected behavior
I'm not quite sure how we should handle lineage for task mapping. At the very least, the lineage for these types of tasks should either be skipped or trigger a warning.
We would like to use the latest version of this plugin which supports Airflow 2.4, but we have several users using dynamic task mapping which would break their tasks.
Desktop (please complete the following information):
Linux Ubuntu - using Airflow's official docker image
The text was updated successfully, but these errors were encountered:
hsheth2
added
accepted
An Issue that is confirmed as a bug by the DataHub Maintainers.
ingestion
PR or Issue related to the ingestion of metadata
labels
Dec 6, 2022
I looked into this briefly and it seems like we can't update task properties when the operator is a MappedOperator. I've asked a question related to this issue in an existing Airflow issue: apache/airflow#24547 (comment)
As a temporary workaround, we filter our mapped tasks by checking isinstance(task, MappedOperator) before the code here:
Yep that workaround seems pretty reasonable, and a PR would be great! We’ll probably want to print a warning and add a note in the docs for this as well - happy to provide guidance on that.
Talked to the Airflow folks about the issue, I'll be putting up a PR to allow setting those properties on MappedOperators. It's been labelled a feature so not sure when it will be released..
Describe the bug
Any DAG task using Airflow's dynamic task mapping will crash when using the Airflow plugin as it can't set the on success/failure callbacks.
Versions:
apache-airflow==2.4.2
acryl-datahub-airflow-plugin==0.9.2.2
Here is an example stacktrace:
To Reproduce
Steps to reproduce the behavior:
Here is a basic DAG that crashes when trying to run with Datahub configured as the lineage backend (using the plugin).
It seems like this bug has been reported in the past as well: #5583
Expected behavior
I'm not quite sure how we should handle lineage for task mapping. At the very least, the lineage for these types of tasks should either be skipped or trigger a warning.
We would like to use the latest version of this plugin which supports Airflow 2.4, but we have several users using dynamic task mapping which would break their tasks.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: