[
https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657717#comment-15657717
]
ASF GitHub Bot commented on KAFKA-4379:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/2103
> 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.2.0
>
>
> 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)