[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: |
|
||||||||||||||||||||
| 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). Notes |
| 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. |