Project

General

Profile

Actions

action #121048

closed

coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

coordination #92854: [epic] limit overload of openQA webUI by heavy requests

action #97190: Limit size of initial requests everywhere, e.g. /, /tests, etc., over webUI and API

action #119428: Ensure users can get all the data for limited queries, e.g. with pagination

Add pagination for GET /api/v1/bugs

Added by kraih about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-11-22
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Proper pagination is planned for every query and API route in #119428. After #120841 has been implemented we now have a prototype to replicate. So this needs to be done for GET /api/v1/bugs.

Acceptance criteria

  • AC1: API endpoint GET /api/v1/bugs has pagination

Suggestions

  • Use limit/offset query parameters and prev/next/first relations in Link headers
  • If possible use the DBIx::Class features for limit and offset

Related issues 2 (1 open1 closed)

Copied from openQA Project - action #120841: Add pagination for GET /api/v1/assets size:MResolvedkraih2022-11-22

Actions
Copied to openQA Project - action #121099: Add pagination for GET /api/v1/jobs/<job_id:num>/commentsNew

Actions
Actions #1

Updated by kraih about 1 year ago

  • Copied from action #120841: Add pagination for GET /api/v1/assets size:M added
Actions #2

Updated by kraih about 1 year ago

  • Status changed from New to In Progress
Actions #3

Updated by okurz about 1 year ago

@kraih I think the existing issues in our backlog are at least equally important so I suggest to not add this ticket to the backlog immediately. And in particular for feature requests I suggest to properly estimate first before starting the work.

Actions #4

Updated by kraih about 1 year ago

okurz wrote:

@kraih I think the existing issues in our backlog are at least equally important so I suggest to not add this ticket to the backlog immediately. And in particular for feature requests I suggest to properly estimate first before starting the work.

I hope you realise that this will make me not split up larger tickets in the future. I'm trying hard here to use the ticket system properly and reduce subtasks to something easily estimatable, despite hating Redmine with a passion. If that means extra long turnaround times because subtasks have to reach the ready queue again, there is no incentive to do it. Anyway... the PR was already half finished when i saw your comment, and is kinda important since it moves the Link header code from #120841 into a shared helper. https://github.com/os-autoinst/openQA/pull/4934

Actions #5

Updated by kraih about 1 year ago

  • Copied to action #121099: Add pagination for GET /api/v1/jobs/<job_id:num>/comments added
Actions #6

Updated by kraih about 1 year ago

  • Status changed from In Progress to Feedback
Actions #7

Updated by kraih about 1 year ago

  • Status changed from Feedback to Resolved
Actions #8

Updated by okurz about 1 year ago

  • Due date deleted (2022-12-07)
Actions

Also available in: Atom PDF