Betterize dataset update blurb#26878
Merged
bbovenzi merged 4 commits intoapache:mainfrom Oct 13, 2022
Merged
Conversation
Contributor
|
8e7e27e to
a6ba077
Compare
dstandish
approved these changes
Oct 13, 2022
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a follow-up PR to #26815. I will rebase this on
mainafter that PR is merged.In that PR, in the DAGs view, we display "X of Y Datasets" for all DAGs that are scheduled on one or more datasets.
This is functionally useful except for datasets that are only ever triggered on one dataset. In that case, as long as the consuming DAG isn't paused and isn't currently running (maybe), the Next Run column will always display "0 of 1 Datasets".
Instead of doing that, for DAGs that consume only one dataset, we now simply show that URI:
The merge commit for this should also be cherry-picked after that merge commit.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.