[MAGNOLIA-8010] Make possible to configure execution of update tasks Created: 25/Feb/21  Updated: 25/Aug/21  Resolved: 25/Aug/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Adam Siska Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLPN-535 Task 'Change structure of mgnl:person... Closed
relates to MGNLPN-536 Task 'Change structure of mgnl:segmen... Closed
relation
is related to MAGNOLIA-5859 Further prevent unsafe usages of Quer... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

There are some update tasks that could take long time to proceed on huge repositories or affect data. There should be a way to configure particular task to be omitted by configuration (e.g. magnolia.properties).
For more info see discussion and linked tickets:
https://git.magnolia-cms.com/projects/MODULES/repos/dam/pull-requests/198/overview?commentId=74545

Notes
When using NodeVisitorTask it can be common to start at the root node. This can lead to extended wait times as we see in MGNLPN-535 & MGNLPN-536



 Comments   
Comment by Simon Lutz [ 25/Aug/21 ]

We do not have any tasks that should be skipped; we should rather make execution of update tasks more efficient.

Linked MGNLPN-tickets are slow because they go through all system nodes. Consider using query tasks.

Generated at Mon Feb 12 04:28:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.