You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2020/05/15 02:03:00 UTC

[jira] [Resolved] (KAFKA-4887) Enabling caching on a persistent window store breaks support for duplicate insertion

     [ https://issues.apache.org/jira/browse/KAFKA-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias J. Sax resolved KAFKA-4887.
------------------------------------
    Resolution: Fixed

> Enabling caching on a persistent window store breaks support for duplicate insertion
> ------------------------------------------------------------------------------------
>
>                 Key: KAFKA-4887
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4887
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.0
>            Reporter: Elias Levy
>            Priority: Major
>
> {{CachingWindowStore}} and {{RocksDBWindowStore}} interact badly when duplicate insertion support is enabled by passing {{true}} as the fourth argument to {{windowed}} in the state store supplier.
> When the feature is enabled, {{RocksDBWindowStore}} correct handles duplicates by assigning a unique sequence number to each element on insertion and using the number within the key.
> When caching is enabled by calling {{enableCaching}} on the supplier, {{CachingWindowStore}} fails to the the same.  Thus, of multiple values inserted with the same key, only the last one survives.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)