[MGNLDAM-1027] DAM search improvement Created: 10/May/22  Updated: 04/Aug/22  Resolved: 18/May/22

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 3.0.15
Fix Version/s: 3.0.16

Type: Improvement Priority: Neutral
Reporter: Jesus Alonso Assignee: Jesus Alonso
Resolution: Fixed Votes: 0
Labels: VN-Testing
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 3h Time Spent: 3h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLDAM-1028 Coding Sub-task Closed Jesus Alonso  
MGNLDAM-1029 piQA Sub-task Closed Yen Lac Tue  
MGNLDAM-1030 QA Sub-task Completed Thuy To  
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)
Epic Link: AuthorX improvements
Sprint: AuthX 9
Story Points: 1
Team: AuthorX

 Description   

Checking MGNLDAM-1016, we detected that AssetListDataProvider.fetchFromBackEnd is called 4 times for each search as we can see in this video -> https://drive.google.com/file/d/1JEEormcz7dtmFn3cDaeDj9ttqu69t1Dl/view?usp=sharing

There are, in fact, 2 different searches all coming from vaddin. I don't understand why vaadin triggers the same search twice. And each search request produces 2 fetchFromBackEnd, one for obtaining the size of the result and another for the content.

As an improvement, we could temporary cache the result of fetchFromBackEnd, so there will only really be 1 fetchFromBackEnd request.


Generated at Mon Feb 12 05:05:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.