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

   ### Apache Airflow version
   
   2.6.1
   
   ### What happened
   
   When using search filters for pages accessible from the `Browse` context 
menu (i.e. `Browse > DAG Runs`), some filters do not seem to apply. Instances 
of this are clearest with filtering by logical date which returns all DAG Runs, 
with the ones matching the filter generally being towards the top. This can 
also be seen on the Variables page using the `ends with` filter.
   
   ### What you think should happen instead
   
   When a filter is applied, it appropriately filters out the rows that do not 
meet the filter and only those that do are shown.
   
   ### How to reproduce
   
   1. Have DAG Runs across multiple logical dates
   2. Go to `Browse > DAG Runs`
   3. Filter based on a logical date (i.e. greater than 2023-05-31 12:00 AM)
   4. Scroll to see that extraneous data is included
   
   ### Operating System
   
   CentOS Linux 7 (Core)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   Installed on a miniconda environment running Python 3.9
   
   ### Anything else
   
   Not all filters seem to be broken. "Starts with" seems to work well, 
meanwhile "Ends with" does not. They both do add a request to the URL, however 
the "ends with" one seems to add `?_flt_undefined_key=` whereas the "starts 
with" adds `?_flt_0_key=`. The filters that do not work also do not appear on 
the filter list.
   
   ### 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