-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Allow Dynamic Tasks to be Searchable Using map_index_template #45109
Merged
jscheffl
merged 1 commit into
apache:main
from
jscheffl:feature/allow-search-via-map-index-template
Dec 20, 2024
Merged
Allow Dynamic Tasks to be Searchable Using map_index_template #45109
jscheffl
merged 1 commit into
apache:main
from
jscheffl:feature/allow-search-via-map-index-template
Dec 20, 2024
Conversation
This file contains 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
shahar1
approved these changes
Dec 20, 2024
Backport failed to create: v2-10-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 16e8a26 v2-10-test This should apply the commit to the v2-10-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
jscheffl
added a commit
that referenced
this pull request
Dec 20, 2024
LefterisXefteris
pushed a commit
to LefterisXefteris/airflow
that referenced
this pull request
Jan 5, 2025
agupta01
pushed a commit
to agupta01/airflow
that referenced
this pull request
Jan 6, 2025
got686-yandex
pushed a commit
to got686-yandex/airflow
that referenced
this pull request
Jan 30, 2025
40 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:dynamic-task-mapping
AIP-42
area:webserver
Webserver related Issues
backport-to-v2-10-test
Mark PR with this label to backport to v2-10-test branch
legacy ui
Whether legacy UI change should be allowed in PR
type:bug-fix
Changelog: Bug Fixes
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.
I know we should not add "new features" to the legacy UI - but just took a look and realized that this request is actually a single-line change. So I propose to "just make it". Also I see this quite useful in my daily life.
closes: #45100