[MGNLPER-141] Performance of JcrSearchResultSupplier#search could be improved using limitPerSupplier from SearchQuery Created: 09/Jul/20  Updated: 10/Jul/20  Resolved: 10/Jul/20

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Type: Improvement Priority: Neutral
Reporter: Antonín Juran Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: 1.25h
Original Estimate: Not Specified

Issue Links:
Issue split
split from MGNLPER-135 Long running searches cause performan... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Maintenance 15
Story Points: 3

 Description   

JcrSearchResultSupplier executes search with limit configured in resultLimit property in JcrSearchResultSupplierDefinition (by default 100) but number of results displayed in UI is limited with limitPerSupplier from SearchQuery (3 for the initial search after logging in to Admin Central, 10 for a search in Find Bar). Search performance could be using the limitPerSupplier in query statement instead of the resultLimit.


Generated at Mon Feb 12 10:29:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.