Feature #1372
closed
GA - technical improvements from Promodo
Added by Anonymous over 4 years ago. Updated almost 4 years ago.
Description
Technical requirements - https://docs.google.com/document/d/1ATwGD2ev9ZLrH_LrHu0K8nDfz27x4j1AnFclUU_QCp4/edit
You don't need to do the code in red.
Files
| Screenshot_6.jpg (157 KB) Screenshot_6.jpg | Anonymous, 23 Dec 2021 07:50 AM | ||
| Screenshot_7.jpg (214 KB) Screenshot_7.jpg | Anonymous, 23 Dec 2021 07:54 AM |
Updated by Anonymous over 4 years ago
- Subject changed from GA - technical improvments from Promodo to GA - technical improvements from Promodo
Updated by Anonymous over 4 years ago
- Description updated (diff)
- Assignee changed from Mykola Romanov to Yevgen Voronetskyy
Updated by Yevgen Voronetskyy over 4 years ago
- Status changed from New to In Progress
- Assignee changed from Yevgen Voronetskyy to Anonymous
- The specification is not clear about 'Category 1/Subcategory 11' - it's universe/subUniverse ?
- if brend field is empty, what should we do ?
Updated by Yevgen Voronetskyy over 4 years ago
workload estimate¶
- link the family/universe graph to productDTO - 9 days
- add jUnit tests - 1 day
- modify 7 scripts/steps described in spec - 2 days
Total: 12 days
Updated by Yevgen Voronetskyy about 4 years ago
Updated by Yevgen Voronetskyy about 4 years ago
updated workload estimate¶
As we agreed with @o.skrypek during today call, we will fix the issue described in precedent note for 4.5 d
- link the family/universe graph to productDTO - 4.5 days
- add jUnit tests - 1 day
- modify 7 scripts/steps described in spec - 2 days
Total: 7.5 days
Updated by Mykola Romanov
Updated by Anonymous almost 4 years ago
Please, write the categories in ukr language.
Updated by Anonymous almost 4 years ago
- File Screenshot_6.jpg Screenshot_6.jpg added
- File Screenshot_7.jpg Screenshot_7.jpg added
We don't have the information about Brand, I think starting from all checkout process. In the screenshot there is information about created orders, there is no Brands. Only default values.
Also we have too much Default categories during the day (not just after restart). I check the products what was bought and saw that there is no breadcrumbs for some period of time for these products.
Ex:
11659284
Updated by Yevgen Voronetskyy almost 4 years ago
Workaround for failed family fetching from OPUS¶
The breadcrumbs generation relays 100% on OPUS fetching. For unknown reasons, random families and even universes failed to be fetched from OPUS. The breadcrumbs for concerning products are null before next server restart.
We propose to store the generated breadcrumbs graph on the file system and update it during the dynamic fetching.
This solution will allow us to ALWAYS have the breadcrumbs.
workload estimate¶
- developing of new architecture for breadcrumbs - 4 dyas
- jUnit tests - 1 days
Total: 5 days
Updated by Yevgen Voronetskyy almost 4 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Dev is done for the first part. Fix for null brand name on payment page is in master.
Updated by Yevgen Voronetskyy almost 4 years ago
- Status changed from Resolved to In Progress
- Assignee changed from Anonymous to Yevgen Voronetskyy
- % Done changed from 100 to 50
Updated by Olek Mark almost 4 years ago
New settings:
breadcrumbs.backup.full-filename:breadcrumbs.json - Breadcrumbs repository full file name (Read/Write access is a must) job.breadcrumbs.delay.initial.in.millis:120000 - time before service start (earlier it was hardcoded) job.breadcrumbs.generation-check-interval.in.millis:10000 - time between generation process observation checks (earlier it was hardcoded)
Updated by Yevgen Voronetskyy almost 4 years ago
- Status changed from In Progress to Resolved
- Assignee changed from Yevgen Voronetskyy to Anonymous
- % Done changed from 50 to 100
Part 2 of the task (breadcrumbs persistence) is done and deployed on production yesterday.