kawatatatsuya commented on issue #56840:
URL: https://github.com/apache/airflow/issues/56840#issuecomment-3446781025
@amoghrajesh
Sorry for the late reply!
After investigating version 2 and version 3, I found that it was working
without any issues. The results of my investigation are as follows.
| Condition
| Airflow 2 | Airflow 3 | Notes
|
|
----------------------------------------------------------------------------------------------
| ---------- | ---------- | --------------------------------------- |
| `dag_a` and `dag_b` start with the same schedule
| ✅ | ✅ | -
|
| `dag_a` and `dag_b` have different schedules and
`include_prior_dates=False` | ✅ | ✅ | -
|
| `dag_a` and `dag_b` have different schedules and
`include_prior_dates=True` | ✅ | ❌ | In v3,
`dag_b` cannot receive XCom |
| `dag_b` is triggered manually and `include_prior_dates=False`
| ✅ | ✅ | -
|
| `dag_b` is triggered manually and `include_prior_dates=True`
| ✅ | ❌ | In v3, `dag_b` cannot receive
XCom |
This is my first contribution to an open-source project, so I would like to
see it through to the end if possible. However, I tried adding a log to
xcom_pull in airflow/models/taskinstance.py as an experiment, but it hasn’t
been output to the terminal or under AIRFLOW_HOME/logs, so I’m still
troubleshooting.
Do you have a solution for this?
Thank you!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
