Project

General

Profile

Bug #10014

Content View Versions api should be paginated but isn't (performance issue)

Added by Partha Aji almost 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1192162
Description of problem:

Currently the content view versions api (which is used by the content view versions list) is not paged. This leads to performance issues with lots of versions.

Version-Release number of selected component (if applicable):

How reproducible:
Always

Steps to Reproduce:
1. Try to fetch a list of content view versions for a content view with over 50 content views

Actual results:
Get all versions and may take a while

Expected results:
Should be 'fast' and only return one pages worth of data (like all other apis)

Additional info:

related to https://bugzilla.redhat.com/show_bug.cgi?id=1161636

Associated revisions

Revision 15b8f9f1 (diff)
Added by David Davis almost 8 years ago

Fixes #10014 - Move version api to scoped search BZ1192162

Revision 2a107074
Added by David Davis almost 8 years ago

Merge pull request #5167 from daviddavis/temp/20150402172023

Fixes #10014 - Move version api to scoped search BZ1192162

History

#1 Updated by The Foreman Bot almost 8 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 68
  • Pull request https://github.com/Katello/katello/pull/5167 added
  • Pull request deleted ()

#2 Updated by Eric Helms almost 8 years ago

  • Legacy Backlogs Release (now unused) set to 31
  • Triaged changed from No to Yes

#3 Updated by Eric Helms almost 8 years ago

  • Target version deleted (68)

#4 Updated by David Davis almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF