-
Notifications
You must be signed in to change notification settings - Fork 13.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
Add ability to filter DAGs in DAGs View by tags using "AND" instead of default behavior "OR" #38147
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
@understructure would you like me to assign this task to you? |
Hello, could a colleague (@TiDeane) and I be assigned to this issue? We are working for a university project and would be grateful to implement this feature. Thank you in advance. |
@RNHTTR I'd love to but unfortunately this is a really inopportune time for me :( |
No problem! Come back to the project when you have some more time!
Done! |
Co-authored-by: Francisco Fonseca <franciscodiasfonseca@tecnico.ulisboa.pt>
Co-authored-by: Francisco Fonseca <franciscodiasfonseca@tecnico.ulisboa.pt>
Description
In the DAGs View, we can enter tags in the "Filter DAGs by tag" box by entering one or more tags. However, this results in an OR-type behavior, where the results show every DAG with any of the entered tags.
With this feature enabled, the list of DAGs returned would be a list only of those DAGs containing ALL of the user-entered tags, rather than a list of DAGs containing ANY of the user-entered tags.
Use case/motivation
This feature could be as simple as adding a checkbox next to the "Filter DAGs by tag" box (marked "use AND" or similar). This will be a great help to filter DAGs when tagging is used extensively and there are hundreds of DAGs on an instance. For instance, we're migrating legacy ELT procedures that use legacy systems. We're tagging these DAGs with all the legacy systems they use. If we could zero in on which DAGs are using legacy system A and legacy system B, it would help us to understand the relationships between those systems, and what needs to be done to no longer rely on either.
Related issues
None I'm aware of.
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: