When multiple filters selected in arg_tags_filter, each filter works as 'or' instead of 'and'.

[oboki]

Description

When I selected multiple filters, it seemed that the tag filter didn't work as I thought. so I checked the query and found that the query uses in clause.

SELECT dag.dag_id AS dag_dag_id, dag.root_dag_id AS dag_root_dag_id, dag.is_paused AS dag_is_paused, dag.is_subdag AS dag_is_subdag, dag.is_active AS dag_is_active, dag.last_scheduler_run AS dag_last_scheduler_run, dag.last_pickled AS dag_last_pickled, dag.last_expired AS dag_last_expired, dag.scheduler_lock AS dag_scheduler_lock, dag.pickle_id AS dag_pickle_id, dag.fileloc AS dag_fileloc, dag.owners AS dag_owners, dag.description AS dag_description, dag.default_view AS dag_default_view, dag.schedule_interval AS dag_schedule_interval 
FROM dag 
WHERE dag.is_subdag = 0 AND dag.is_active = 1 AND (EXISTS (SELECT 1 
FROM dag_tag 
WHERE dag.dag_id = dag_tag.dag_id AND dag_tag.name IN (%s, %s)))

Use case / motivation

I want this filter to work with the 'and' condition. and I think 'and' condition is more familiar with the filter function.

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[kaxil]

cc @ryanahamilton Our author of the filter :) Was this intentional ?

[ryanahamilton]

@kaxil I think you might be mixing this up with the status filter I added. The tags filter was added shortly before by @zacharya19 in #6489. What say you @zacharya19?

[kaxil]

aah sorry for the mixup :)

[zacharya19]

@kaxil Yep, it was intentional.
What I had in mind is a tag per "team", so it make sense to me it will be "OR".
I think we should add a config option to control the default behavior and maybe an option to choose it in the UI.

[tschroeder-zendesk]

Fairly old issue, but it would be really helpful if we could use AND or have an option in our case we have about 400 dags and we are generally only working with a handful of them. We have them tagged as 3 different things pod/cluster/state and would be great if we could easily say I want all cluster=green AND pod=13 for example instead of the current workaround which means we will need to add a bunch of superfluous tags that have the combo options so we can see a nice slice of dags.

[kacpermuda]

Totally agree, we are in a very similar situation. We have plenty of dags and we use tags to group them by client, environment, service they are using etc. It would be perfect option for our use case to use AND operator in tags, so that we can choose a small subset of dags f.e. all dags that use certain api for given client.

[potiuk]

Just repeating myself - but Airflow is created by >2100 contributors - mostly users who want to solve their problems.

Contributions are most welcome and if any of the people here would like to go an extra mile (or rather foot) to add this as a feature - you are most welcome!

This is the fastest and most certain way to get it implemented.

[kacpermuda]

I can see that a decision has been made to implement this feature as a part of UI part (see PR #25437). Is there anything i can do, as a Python dev that has no skills in the UI area, to help in this implementation?