[MGNLPER-134] JcrSearchResultSupplier not considering NodeType constraint in query Created: 18/Jun/20  Updated: 16/Jul/20  Resolved: 02/Jul/20

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

Type: Bug Priority: Major
Reporter: Sönke Schmidt Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: 0d
Time Spent: 1.5d
Original Estimate: Not Specified

Issue Links:
Relates
relation
is related to 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Maintenance 14
Story Points: 3

 Description   

The JcrSearchResultSupplierDefinition allows the specification of a NodeType constraint.

However this constraint is not considered in the construction of the JCR Query in info.magnolia.periscope.search.jcr.JcrSearchResultSupplier. Even though the method runQuery(...) contains code to create this constraint, it is not part of the final query.
Only after the query has been executed, the result is being filtered by the specified NodeTypes.

Depending on the size of the queried workspace this may result in substantially longer query times and performance issues.
In our case the website workspace contains around 45,000 nodes. The initial query without the NodeType constraint took around 10 - 15 seconds, as the supplier queried for [nt:base] instead of [mgnl:page]

Please make the NodeType constraint part of the constructed query.


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