Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-5967

Investigate whether we should publish methods on services to flush caches

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Complete
    • Affects Version/s: 2.0.0-b1
    • Fix Version/s: 2.0.0-b6, 2.0
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Currently cache's are flushed on update and create methods, but should we have a method that flushes the cache with a call? It seems possible that some institutions would have a batch job that doesn't use the service for crud (db updates?), and it seems like in that instance there should be an easier way for them to clear the cache.

        Attachments

          Activity

          Hide
          ewestfal Eric Westfall added a comment -

          Bulk update of incomplete 2.0.0-b2 issues to just a 2.0 fix version.

          Show
          ewestfal Eric Westfall added a comment - Bulk update of incomplete 2.0.0-b2 issues to just a 2.0 fix version.
          Hide
          ewestfal Eric Westfall added a comment -

          My opinion on this is that we should not be doing this as part of the main service contract. As part of some sort of auxiliary administration api, perhaps (assuming it's needed). But I think that the idea with the services is that the caching is an implementation detail so publishing methods to facilitate manual cache flushing on the api constitutes a leaky abstraction to me. I'm going to resolve this issue, but feel free to discuss further if you think otherwise.

          Show
          ewestfal Eric Westfall added a comment - My opinion on this is that we should not be doing this as part of the main service contract. As part of some sort of auxiliary administration api, perhaps (assuming it's needed). But I think that the idea with the services is that the caching is an implementation detail so publishing methods to facilitate manual cache flushing on the api constitutes a leaky abstraction to me. I'm going to resolve this issue, but feel free to discuss further if you think otherwise.
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

            • Assignee:
              jjhanso Jeremy Hanson
              Reporter:
              jjhanso Jeremy Hanson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: