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

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   3.2
   
   ### What happened and how to reproduce it?
   
   Use latest(3.2) airflow docker image, docker compose can look like this:
   ```yaml
     airflow.localhost:
       image: apache/airflow:latest
       command: airflow standalone
       ports: "8080:8080"
   ```
   
   Create any dummy dag and run it two times specifying `run_id` manually, for 
example `10` and `11`
   
   Using rest api v2 run:
   ```bash
   curl 
'http://localhost:8080/api/v2/dags/dag_name/dagRuns?run_id_pattern=10|11'
   ```
   
   Empty list is returned while **it should return two dag runs according to 
rest api docs**.
   
   Interestingly when not using or but just this:
   ```bash
   curl 'http://localhost:8080/api/v2/dags/dag_name/dagRuns?run_id_pattern=10'
   ```
   It works as expected returning dag run with run_id `10`
   
   using encoded pipe with `run_id_pattern=11%7C10` does not help either
   
   ### What you think should happen instead?
   
   _No response_
   
   ### Operating System
   
   _No response_
   
   ### Deployment
   
   None
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### 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