Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-41861

Hierarchy cache missing invalidation when children change

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 19.0, 19.1, 19.2, 20.0 [Tentative]
    • Fix Version/s: 20.0 [Tentative]
    • Component/s: Hierarchy
    • Labels:
    • 19 status:
      Please Merge
    • Test Plan:
      Hide

      Please add a Test Plan here.

      Show
      Please add a Test Plan here.

      Description

      We have a quartz job that creates our Evaluation site hierarchy that isn't working correctly after the cache was introduced (SAK-33574). 

      The problem is that when inserting a new node, we call HierarchyService.getChildNodes() in order to traverse the tree to find the desired parent.  If that parent was just created by the job, it is not included in the list of children because that list is coming from the cache, which hasn't been updated.

      I think we need to invalidate the cached children when a new one is added or removed.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  curtisvo Curtis van Osch
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code