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

Posted to jira@kafka.apache.org by "Maatari (Jira)" <ji...@apache.org> on 2020/03/28 05:41:00 UTC

[jira] [Commented] (KAFKA-4587) Rethink Unification of Caching with Dedupping

    [ https://issues.apache.org/jira/browse/KAFKA-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069241#comment-17069241 ] 

Maatari commented on KAFKA-4587:
--------------------------------

Hi all, i'm note sure to follow what is the status of this ticket. Is it still relevant ?

> Rethink Unification of Caching with Dedupping
> ---------------------------------------------
>
>                 Key: KAFKA-4587
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4587
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Guozhang Wang
>            Priority: Major
>
> This is discussed in PR https://github.com/apache/kafka/pull/1588
> In order to support user-customizable state store suppliers in the DSL we did the following:
> 1) Introduce a {{TupleForwarder}} to forward tuples from cached stores that is wrapping user customized stores.
> 2) Narrow the scope to only dedup on forwarding if it is the default CachingXXStore with wrapper RocksDB. 
> With this, the unification of dedupping and caching is less useful now, and we are complicating the inner implementations for forwarding a lot. We need to re-consider this feature with finer granularity of turning on / off caching per store, potentially with explicit triggers.



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