You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "dstandish (via GitHub)" <gi...@apache.org> on 2026/01/26 15:00:50 UTC
[I] Determine what next execution should do for partition-driven dags [airflow]
dstandish opened a new issue, #61076:
URL: https://github.com/apache/airflow/issues/61076
### Body
CLI action dag_next_execution prints next execution for logical date dags. Need to assess what to do for partition-driven and implement.
### Committer
- [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project.
--
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: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Determine what next execution should do for partition-driven dags [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on issue #61076:
URL: https://github.com/apache/airflow/issues/61076#issuecomment-3944469410
OK I think this is what I’m going to do. To be honest I feel the current `dag_next_execution` output isn’t that useful to begin with. I want it to be able to show more fields. So I’m thinking
* Deprecate the current `airflow dags next-execution dag-id` without additional flags (we’ll maybe change it to show one of the followings in 4.0)
* Add `--table` to show a table of values. Probably include the logical date, data interval start and end, run_after, and the partition key.
* Add `--value=<attr>` to show only one of the above value.
How does this sound?
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Determine what next execution should do for partition-driven dags [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on issue #61076:
URL: https://github.com/apache/airflow/issues/61076#issuecomment-3944487067
Also probably add some more fields to `dag_list_dag_run` to match the format.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Determine what next execution should do for partition-driven dags [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on issue #61076:
URL: https://github.com/apache/airflow/issues/61076#issuecomment-3949219678
`dag_list_dag_runs` also currently misses data interval fields so we might want to add them too.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Determine what next execution should do for partition-driven dags [airflow]
Posted by "shleshaG (via GitHub)" <gi...@apache.org>.
shleshaG commented on issue #61076:
URL: https://github.com/apache/airflow/issues/61076#issuecomment-3828021549
I understand that dag_next_execution currently works for logical-date–based DAGs, and the open question is how it should behave for partition-driven DAGs. I’m happy to take this up. Before implementing, I just wanted to confirm the expected behavior for partition-driven DAGs , for example, should the CLI:
1. compute the next available partition,
2. display a placeholder / informative message or intentionally skip output if it’s not well-defined?
Once the intended semantics are clear, I can proceed with the implementation and open a PR accordingly.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Determine what next execution should do for partition-driven dags [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr closed issue #61076: Determine what next execution should do for partition-driven dags
URL: https://github.com/apache/airflow/issues/61076
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Determine what next execution should do for partition-driven dags [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on issue #61076:
URL: https://github.com/apache/airflow/issues/61076#issuecomment-3882930255
I think the CLI should compute the partition that would be satisfied by the next scheduled run. I also think the message should be different to make clear this is showing a partition.
Not sure what you mean by _not well-defined_. Can you clarify? If a next partition cannot be determined, a warning should be shown similar to how we notify about non-time-based schedules.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Determine what next execution should do for partition-driven dags [airflow]
Posted by "Lee-W (via GitHub)" <gi...@apache.org>.
Lee-W commented on issue #61076:
URL: https://github.com/apache/airflow/issues/61076#issuecomment-3944846133
> How does this sound?
yep
> dag_list_dag_run
probably add `partition_key` there as well? anything else you're considering?
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org