You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "shleshaG (via GitHub)" <gi...@apache.org> on 2026/02/01 12:58:27 UTC
[PR] Clarify warning for partition-driven DAGs in dags next-execution [airflow]
shleshaG opened a new pull request, #61319:
URL: https://github.com/apache/airflow/pull/61319
What does this PR do?
Clarifies the warning message shown by `airflow dags next-execution` when no next
data interval can be determined, noting that this can also occur for
dataset- or partition-driven DAGs.
Why is this needed?
With AIP-76, partition-driven and dataset-driven DAGs may not have a
determinable next execution date. The previous message only mentioned
`@once` or `None` schedules, which could be misleading.
This change improves CLI clarity without altering behavior.
How was this tested?
- Manual verification of CLI output
Related issue
- 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: [PR] Clarify warning for partition-driven DAGs in dags next-execution [airflow]
Posted by "boring-cyborg[bot] (via GitHub)" <gi...@apache.org>.
boring-cyborg[bot] commented on PR #61319:
URL: https://github.com/apache/airflow/pull/61319#issuecomment-3831013469
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:
- Pay attention to the quality of your code (ruff, mypy and type annotations). Our [prek-hooks]( https://github.com/apache/airflow/blob/main/contributing-docs/08_static_code_checks.rst#prerequisites-for-prek-hooks) will help you with that.
- In case of a new feature add useful documentation (in docstrings or in `docs/` directory). Adding a new operator? Check this short [guide](https://github.com/apache/airflow/blob/main/airflow-core/docs/howto/custom-operator.rst) Consider adding an example DAG that shows how users should use it.
- Consider using [Breeze environment](https://github.com/apache/airflow/blob/main/dev/breeze/doc/README.rst) for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
- Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
- Please follow [ASF Code of Conduct](https://www.apache.org/foundation/policies/conduct) for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
- Be sure to read the [Airflow Coding style]( https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#coding-style-and-best-practices).
- Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
Apache Airflow is a community-driven project and together we are making it better 🚀.
In case of doubts contact the developers at:
Mailing List: dev@airflow.apache.org
Slack: https://s.apache.org/airflow-slack
--
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: [PR] Clarify warning for partition-driven DAGs in dags next-execution [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr closed pull request #61319: Clarify warning for partition-driven DAGs in dags next-execution
URL: https://github.com/apache/airflow/pull/61319
--
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: [PR] Clarify warning for partition-driven DAGs in dags next-execution [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #61319:
URL: https://github.com/apache/airflow/pull/61319#issuecomment-3841004889
Actualy - the right fix here will be to remove interval. In Airflow 3 we have `schedule` as the preferred way to specify schedule - other past ways are deprecated, so just removing interval will be enough - adding almost the same thing twice is quite confusing
--
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: [PR] Clarify warning for partition-driven DAGs in dags next-execution [airflow]
Posted by "shleshaG (via GitHub)" <gi...@apache.org>.
shleshaG commented on PR #61319:
URL: https://github.com/apache/airflow/pull/61319#issuecomment-3841189369
@potiuk Thanks a lot for the clarification! That makes sense — I see now that updating the warning text alone is not sufficient.
Based on your guidance, I’ll update the implementation to remove usage of `interval` and rely solely on `schedule`, which aligns with the Airflow 3 scheduling model. I’ll push an updated commit shortly. Please let me know if there’s anything else I should watch out for.
--
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: [PR] Clarify warning for partition-driven DAGs in dags next-execution [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on code in PR #61319:
URL: https://github.com/apache/airflow/pull/61319#discussion_r2791920766
##########
airflow-core/src/airflow/cli/commands/dag_command.py:
##########
@@ -336,6 +336,7 @@ def print_execution_interval(interval: DataInterval | None):
print(
"[WARN] No following schedule can be found. "
"This DAG may have schedule interval '@once' or `None`.",
+ "or have a schedule of '@once' or None.",
Review Comment:
There are actually more cases, once and none are simply the oldest ones (and probably the only ones when this message was first introduced).
Let’s change the entire message to something like _This Dag may have a schedule that is not time-based, such as `None` or `@once`_.
--
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