[
https://issues.apache.org/jira/browse/KAFKA-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468313#comment-15468313
]
Eno Thereska commented on KAFKA-3779:
-------------------------------------
I suggest we wait on adding dedup for (4) until we have obtained more
experience with KIP-63 deployment, and that we keep KIP-63 primarily focused on
(2) above. For (2) the semantics and expected gains are clear. I'm worried that
this will be confusing for (4). [~damianguy] what do you think?
> Add the LRU cache for KTable.to() operator
> ------------------------------------------
>
> Key: KAFKA-3779
> URL: https://issues.apache.org/jira/browse/KAFKA-3779
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Eno Thereska
> Fix For: 0.10.1.0
>
>
> The KTable.to operator currently does not use a cache. We can add a cache to
> this operator to deduplicate and reduce data traffic as well. This is to be
> done after KAFKA-3777.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
