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
DAGs are able to see historical dataset events when created new #39456
Labels
Comments
tosheer
added
area:core
kind:bug
This is a clearly a bug
needs-triage
label for new issues that we didn't triage yet
labels
May 7, 2024
RNHTTR
added
Can't Reproduce
The problem cannot be reproduced
pending-response
area:datasets
Issues related to the datasets feature
and removed
needs-triage
label for new issues that we didn't triage yet
labels
May 7, 2024
I'm not able to reproduce -- I think the context object in the post execute function is incorrect. |
@RNHTTR i have updated the dag definition as i was reproducing issue on local with a more simpler DAG definition. can you please try again and see if you can reproduce the issue. For more details see attached images. |
Logs
|
RNHTTR
removed
Can't Reproduce
The problem cannot be reproduced
pending-response
area:core
labels
May 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Apache Airflow version
2.9.1
If "Other Airflow 2 version" selected, which one?
No response
What happened?
If a new dataset triggreed DAG is created for an already existing dataset. (Dataset has already existing dataset events) DAG see all dataset events from very first event for dataset.
What you think should happen instead?
If a new dataset triggreed DAG is created for an already existing dataset. (Dataset has already existing dataset events). DAG should see all the dataset events from the time when DAG was added.
How to reproduce
After this add
Operating System
Debian GNU/Linux 12 (bookworm)
Versions of Apache Airflow Providers
No response
Deployment
Docker-Compose
Deployment details
Plain vanilla airflow.
Anything else?
This issue is associated with an earlier issue #38826. Fix of that issue just fixed disabled - enabled / deleted - recreated.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: