[FOLIO-2409] Reduce default page size limit.maximum to 1000 in traits/pageable.raml Created: 20/Dec/19  Updated: 10/Aug/20

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Umbrella Priority: P2
Reporter: Julian Ladisch Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: compatibility-breaking, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by RMB-535 SPIKE allow module to set the maximum... Open
Relates
relates to RMB-553 Add postSync to PgUtil Closed
relates to STSMACOM-296 Change ControlledVocab limit from 500... Closed
relates to MODUSERS-170 queries with limit=2147483647 may ret... Open
relates to CIRC-624 circulation/requests endpoint returns... Closed
Sprint: DevOps: Sprint 95
Development Team: Core: Platform

 Description   

Modules fail with out of memory error if a pageable GET endpoint is used for downloading a large recordset at once (for example by using limit=2147483647).

Modules can restrict the maximum page size (limit) on a per API endpoint basis. However, most use the pageable trait from https://github.com/folio-org/raml/blob/raml1.0/traits/pageable.raml where limit.maximum=2147483647; this trait contains the de-facto default that should be changed.

Tasks:

Note: This does not affect streaming APIs. Those don't have this memory problem, don't use paging and don't use the pageable trait.



 Comments   
Comment by Julian Ladisch [ 30/Jan/20 ]

Add a traits/pageable2000.raml for controlled vocabulary, see STSMACOM-296 Closed = https://github.com/folio-org/stripes-smart-components/commit/96672c4729e4cfea73051a6c01390dcefb35257b
Controlled vocabulary has a much smaller record size and therefore can have a bigger page size.

Generated at Thu Feb 08 23:20:26 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.