We have moved to GitHub Issues
Created by Shannon Deminick 31 Jan 2017, 02:46:26 Updated by Sebastiaan Janssen 09 Feb 2017, 20:02:56
Relates to: U4-9494
Relates to: U4-9447
Subtask of: UAASSCRUM-790
When we page data we lookup the document data first, then we lookup the property data. It turns out that when we lookup this property data, the paged subset is not taken into account which means we actually query against all of the property data in the db!
This means that if there is 500,000 rows in the property data, and we are executing a paged query where the page size is only 10 documents, we would still fetch all 500,000 property data rows and then filter then to combine with the 10 documents which obviously is incredibly inefficient. Instead when fetching the property data rows we inner join the query on the paged document dataset to only return the property data rows for the 10 documents.
All seems to work beautifully :)
Backwards Compatible: True
Due in version: 7.5.10
Sprint: Sprint 52