Haapalaj opened a new issue, #48494:
URL: https://github.com/apache/airflow/issues/48494
### Apache Airflow version
2.10.5
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
For Airflow stable API request of listing task instances:
GET
/api/v1/dags/~/dagRuns/~/taskInstances?limit=3&offset=1&order_by=start_date
{
"detail": "Extra query parameter(s) order_by not in spec",
"status": 400,
"title": null,
"type":
"https://airflow.apache.org/docs/apache-airflow/2.10.5/stable-rest-api-ref.html#section/Errors/BadRequest";
}
The list is returned in random order.
### What you think should happen instead?
In the Airflow stable API, the task listing API's should support pagination.
They do support "offset" and "limit" but not the "order_by", which is needed
for pagination.
The list is returned in random order.
Happen s with:
GET
https://airflow.apache.org/api/v1/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances
https://airflow.apache.org/api/v1/dags/~/dagRuns/~/taskInstances/list
and
POST
https://airflow.apache.org/api/v1/dags/~/dagRuns/~/taskInstances/list
### How to reproduce
GET
/api/v1/dags/~/dagRuns/~/taskInstances?limit=3&offset=1&order_by=start_date
### Operating System
linux
### Versions of Apache Airflow Providers
apache-airflow-providers-snowflake==6.1.1
apache-airflow-providers-amazon==9.4.0
apache-airflow-providers-google==14.0.0
apache-airflow-providers-microsoft-azure==12.2.0
apache-airflow-providers-odbc==4.9.0
apache-airflow-providers-postgres==6.1.0
apache-airflow-providers-databricks==7.2.0
### Deployment
Docker-Compose
### Deployment details
_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]
