Azurealistic opened a new issue, #73205:
URL: https://github.com/apache/airflow/issues/73205

   ### Under which category would you file this issue?
   
   Airflow Core
   
   ### Apache Airflow version
   
   3.3.1
   
   ### What happened and how to reproduce it?
   
   Hello, so we have many DAGs with a format of something like: 
`consumer__first_name__task_name__hourly` for example. Previously I could 
search for something like `task` or `first_name` and have the relevant dags 
pop-up automatically. However, after upgrading from Airflow 3.2.1 to Airflow 
3.3.1 (due to CVEs) we noticed that we can no longer perform the search as 
before. Now we have to match the name of the dag exactly. for example, 
`consumer__first_name` to see the same as I saw before with just `first_name`.
   
   This also occurs in the Variables screen.
   
   ### What you think should happen instead?
   
   It should simply search all DAGs that have the relevant string present 
anywhere like it did before instead of only scanning/checking from the first 
character on.
   
   ### Operating System
   
   Ubuntu 22.04.5 LTS
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   Not Applicable
   
   ### Helm Chart configuration
   
   Not Applicable
   
   ### Docker Image customizations
   
   Not Applicable
   
   ### Anything else?
   
   Occurs ever since upgrade to 3.3.1 on any search in the "DAG" or "Variable" 
pages.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to