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

The Internal Cache Registry needs to be persistent

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 8.1.0.Alpha1, 8.1.0.Final
    • None
    • Core
    • None

    Description

      Several improvements suggested by Sanne:

      • protobuf schemas should be persisted, hotrod topology info and security cache should not
      • also for security I want to set lifetime properties

      Attachments

        Issue Links

          incorporates

          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-3747 ProtobufMetadataRegistry should be persistent

          • 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 blocked 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-3351 Controlled cluster shutdown with data restore from persistent storage

          • 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
          relates to

          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-3928 The ClusterRegistry API needs extending to allow put of mortal entries

          • 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.
          • To Do

          Activity

            People

              ttarrant@redhat.com Tristan Tarrant
              mircea.markus Mircea Markus (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: