Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-2595] Update tasks : streamline class names, functionality and provide a couple more useful abstractions Created: 28/Jan/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Sub-task Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-5857 Provide a NodeVisitorTask and emphasi... Closed
relation
is related to MAGNOLIA-2597 Provide a QueryTask - to operate on n... Closed
Template:
Date of First Response:

 Description   
  • current naming is very inconsistent, makes it hard to find the appropriate task to use
  • the way some tasks work is inconsistent with others: some are very safe (check current values, etc), some aren't (just add a property no matter what the current status is) - we should add consistency and/or document the few inconsistency and why the safety is needed in most cases
  • we've often had the need for :
    • tasks which recurse through subnodes - an abstract task using a Visitor would be very helpful.
    • tasks which perform an operation over a given set of nodes - an abstract takes that operates on the nodes returned by a jcr query would help.


 Comments   
Comment by Magnolia International [ 28/Jan/09 ]

There is one issue we might have with MAGNOLIA-2597's QueryTask : since the queries are not seeing the latest changes that a previous task might have done, it might return irrelevant results and make updates fail. One way to make this less flaky might be to save after each delta instead of, as currently done, after all deltas for a module have been executed. This would decrease the likelihood of side-effects caused by updates when intermediate versions are skipped.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:38:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.