Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-424

Add a Cache state API to the Samza container

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • container
    • None

    Description

      There are cases when the user code needs access to a 'cache' which can be used to store custom data. This cache is different from the KeyValue store in the following ways:

      • At the very least Needs to support LRU (Least Recently Used) and TTL (Time To Live) eviction strategies
      • May not support all() and range() operations (since this wreaks havoc with the eviction operation)
      • Needs to exist at a per task or a per container level.

      Attachments

        1. SAMZA-424-Cache-API_2.pdf
          41 kB
          Chinmay Soman
        2. SAMZA-424-Cache-API_2.md
          5 kB
          Chinmay Soman
        3. samza-424-cache-api_1.pdf
          41 kB
          Chinmay Soman
        4. SAMZA-424-Cache-API_1.md
          6 kB
          Chinmay Soman
        5. SAMZA-424-Cache-API_0.pdf
          58 kB
          Chinmay Soman

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SAMZA-428 Investigate: how to tune down caching in the KeyValueStore implementations

          • Major - Major loss of function.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. SAMZA-402 Provide a "shared state" store among StreamTasks

          • Major - Major loss of function.
          • Open

          Activity

            People

              cpsoman Chinmay Soman
              cpsoman Chinmay Soman
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: