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

Create a merge Policy that allow the latest value in cache

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • None
    • None
    • None

    Description

      Per discussion with the dev team,

      We could use versions and/or timestamps to decide which is the "latest" value.
      That there's no way to force all cache entries to have either a version or a timestamp.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. ISPN-7590 Invocation idempotence

          • 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-8680 Provide cache entry meta data without necessity to set expiration

          • 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

              Unassigned Unassigned
              dlovison@redhat.com Diego Lovison
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: