[MGNLDAM-1016] JcrAssetProvider querybuilder performance issues. Created: 24/Mar/22 Updated: 04/Apr/23 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | 3.0.14 |
| Fix Version/s: | 3.0.16 |
| Type: | Bug | Priority: | Major |
| Reporter: | Rico Jansen | Assignee: | Lam Nguyen Bao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | VN-Analysis, cs-bk | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | 7d 1.75h | Time Spent: | 7d 1.75h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||
| 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
|
||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||
| Visible to: |
Mathijn Elhorst, Michiel Meeuwissen, Tim Molenaar
|
||||||||||||||||||||||||||||||
| Epic Link: | AuthorX Support | ||||||||||||||||||||||||||||||
| Sprint: | AuthX 8, AuthX 9, AuthX 10 | ||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||
| Description |
|
After some more testing of our Magnolia 6 instance it was discovered that the asset chooser search options use a querybuilder built into JcrAssetProvider that suffers from similar performance issues as the JcrQueryBuilder ( It also uses non-index queries with a like with wildcards on both ends. Which results in very slow queries. Also why does this not use the JcrQueryBuilder ?, there is a large overlap in the code with that. |