-
Bug
-
Resolution: Fixed
-
Major
-
1.2.1
-
-
Empty show more show less
-
Maintenance 14
-
3
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.
- is related to
-
MGNLPER-135 Long running searches cause performance issues in Admin Central
- Closed