[
https://issues.apache.org/jira/browse/KAFKA-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-6998:
-----------------------------------
Description:
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.
KIP: [KIP-356: Add withCachingDisabled() to
StoreBuilder|https://cwiki.apache.org/confluence/display/KAFKA/KIP-356%3A+Add+withCachingDisabled%28%29+to+StoreBuilder?src=jira]
was:
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.
> 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
> Assignee: Guozhang Wang
> Priority: Major
> Labels: kip
>
> 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.
> KIP: [KIP-356: Add withCachingDisabled() to
> StoreBuilder|https://cwiki.apache.org/confluence/display/KAFKA/KIP-356%3A+Add+withCachingDisabled%28%29+to+StoreBuilder?src=jira]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
