Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-3675

EPersons cached as submitters aren't uncached when their item is

    Details

    • Type: Code Task
    • Status: Volunteer Needed (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 6.2
    • Fix Version/s: 7.0
    • Component/s: DSpace API
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      4
    • Documentation Status:
      Needed

      Description

      To resolve the problems described in DS-3656 and DS-3648 the handling of the hibernate cache was changed (see DSPR#1824). As the changes were introduced into a minor version of DSpace (6.2) we decided to uncache rather sensitively as we did not wanted to introduce new bugs as result from too aggressive uncaching.

      Whenever an item gets loaded, its submitter gets cached. Whenever an item is removed from the cache its submitter isn't as it could be the EPerson that is running the current session (and loaded as context.currentUser). For huge batch processes this may result in a lot of EPersons not being uncached, which we should change. This change should be introduced into a major version of DSpace as new major versions have to succeed in a real testathron.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                pbecker Pascal-Nicolas Becker
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: