Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
None
-
-
Core: Platform
Description
The total records count returned is not exact when there are many records in the database.
zburke summarized the problem:
“When a table has many rows, queries that match N rows AND include a limit clause asking for < N rows receive an inaccurate value for totalRecords. Given that same query and a limit clause that overlaps the actual totalRecords value (e.g. the actual result set has 123 records and the query asks for records 100-200), we receive the correct value for totalRecords."
More context in: MODINVSTOR-414
API call example and result:
https://${okapiUrl}/inventory/instances?limit=30&query=(title="" or contributors adj "\"name\": \"\"" or identifiers adj "\"value\": \"\"") sortby title { "instances" : [ { ... } ], "totalRecords" : 999999999 }
TestRail: Results
Attachments
Issue Links
- relates to
-
MODINVSTOR-414 totalRecords value may be wildly inaccurate for large collections
-
- Closed
-
-
MODINVSTOR-906 Mention that totalRecords may be estimation in RAML json
-
- Closed
-
-
RMB-93 make number of records to get exact count for configurable
-
- Open
-
-
RMB-301 query optimizer hint: sort index or full text index
-
- Closed
-
-
STCON-90 gracefully handle unexpected changes to totalRecords in the middle of paging
-
- Closed
-
-
STSMACOM-259 Instance search result total is wrong when there are 10K+ records in Inventory
-
- Closed
-
-
CHAL-240 Populate HRIDs with Libris XL IDs for Libris records with FOLIO-populated HRIDs
-
- Closed
-
-
CHAL-294 Query request where offset value > totalRecords returns 0 reords even if actual number of records > totalRecords
-
- In Code Review
-
-
MODINVSTOR-468 hitcount related issues in Q1
-
- Closed
-
-
RMB-578 Inform whether totalRecords is exact or an estimate
-
- Blocked
-