You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Damian Guy (JIRA)" <ji...@apache.org> on 2016/11/04 11:48:59 UTC

[jira] [Created] (KAFKA-4379) Remove caching of dirty and removed keys from StoreChangeLogger

Damian Guy created KAFKA-4379:
---------------------------------

             Summary: Remove caching of dirty and removed keys from StoreChangeLogger
                 Key: KAFKA-4379
                 URL: https://issues.apache.org/jira/browse/KAFKA-4379
             Project: Kafka
          Issue Type: Improvement
          Components: streams
    Affects Versions: 0.10.1.0
            Reporter: Damian Guy
            Assignee: Damian Guy
            Priority: Minor
             Fix For: 0.10.1.1


The StoreChangeLogger currently keeps a cache of dirty and removed keys and will batch the changelog records such that we don't send a record for each update. However, with KIP-63 this is unnecessary as the batching and de-duping is done by the caching layer. Further, the StoreChangeLogger relies on context.timestamp() which is likely to be incorrect when caching is enabled



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)