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

Add batching to the AdvancedCacheWriter interface

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 9.1.0.Beta1
    • None
    • Loaders and Stores
    • None

    Description

      The AdvancedCacheWriter should be extended with a batch operation which takes multiple write/remove operations so that stores which can do batching can optimize this. This would benefit:

      • passivateAll
      • putAll
      • the async writer
        Immediate users would be the JDBC stores, JPA, RocksDB.

      Attachments

        Issue Links

          blocks

          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-5210 Support writing multiple modifications to cache stores in batch when using Transactions

          • 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) JDG-1088 Batching support for persistence

          • 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
          is related 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-7936 Add configurable batch-size to AbstractStoreConfiguration

          • 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

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

              Dates

                Created:
                Updated:
                Resolved: