Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5380

Create a registry of internal caches

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 7.2.0.Final
    • None
    • Core
    • None

    Description

      Several parts of the code create caches for internal use (hotrod topology, protobuf schema, scripting cache, recovery, etc). These should all be created through a common interface so that thet can be filtered out when necessary.

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. ISPN-5240 CacheContainer cluster statistics count in entries in internal hotrodTopologyCache

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-5012 ClusterRegistry as a service cache provider

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is duplicated by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-4876 API for obtaining cache metadata

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ttarrant@redhat.com Tristan Tarrant
              ttarrant@redhat.com Tristan Tarrant
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: