[
https://issues.apache.org/jira/browse/KAFKA-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502615#comment-16502615
]
Guozhang Wang commented on KAFKA-6998:
--------------------------------------
I've realized this issue when doing some benchmarks, and did some pokes around.
The tricky thing is that today stores are built in
`internalTopologyBuilder.build()`, while the configs are not passed in to
internalTopologyBuilder yet. So making this change need to poke a hole in the
`build()` function to pass in the configs so that the build process knows about
what config values are to build the store differently.
> Remove caching wrapper stores if cache-size is configured to zero bytes
> -----------------------------------------------------------------------
>
> Key: KAFKA-6998
> URL: https://issues.apache.org/jira/browse/KAFKA-6998
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Major
>
> Users can disable caching globally by setting the cache size to zero in their
> config. However, this does only effectively disable the caching layer, but
> the code is still in place.
> We should consider to remove the caching wrappers completely for this case.
> The tricky part is, that we insert the caching layer at compile time, ie,
> when calling `StreamsBuilder#build()` – at this point, we don't know the
> configuration yet. Thus, we need to find a way to rewrite the topology after
> it is passed to `KafkaStreams` if case caching size is set to zero.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
