[MGNLPER-192] Port to master - JcrSearchResultSupplier generates inefficient queries. Created: 09/May/23  Updated: 19/May/23  Resolved: 19/May/23

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

Type: Bug Priority: High
Reporter: Rico Jansen Assignee: ricardo gonzalez
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLPER-168 JcrSearchResultSupplier generates ine... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Epic Link: [JCR] Search Performance issues
Story Points: 5
Team: AuthorX
Work Started:
Approved:
Yes

 Description   

When generating a query JcrSearchResultSupplier will generate empty wildcard like as a clause when the searchterm is empty. This will create a bad performing query.

It also uses wildcard characters on a fulltext query, which is unnecessary.

Measure and record the times before the change and after the change in this ticket using the big data environment. We have a common place for the metrics here: https://www.notion.so/magnoliacms/Monitoring-and-tracking-metrics-d6c3037f7a584aa79911ecaf3d3bd22f


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