You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Eno Thereska (JIRA)" <ji...@apache.org> on 2016/07/18 22:57:20 UTC
[jira] [Updated] (KAFKA-3778) Avoiding using range queries of
RocksDBWindowStore on KStream windowed aggregations
[ https://issues.apache.org/jira/browse/KAFKA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eno Thereska updated KAFKA-3778:
--------------------------------
Summary: Avoiding using range queries of RocksDBWindowStore on KStream windowed aggregations (was: Avoidin using range queries of RocksDBWindowStore on KStream windowed aggregations)
> Avoiding using range queries of RocksDBWindowStore on KStream windowed aggregations
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-3778
> URL: https://issues.apache.org/jira/browse/KAFKA-3778
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Eno Thereska
> Fix For: 0.10.1.0
>
>
> RocksDbWindowStore currently does not use caches, but its window segments implemented as RocksDbStore does. However, its range query {{fetch(key, fromTime, toTime)}} will cause all its touched segments' cache to be flushed.
> After KAFKA-3777, we should change its implementation for KStreamWindowAggregation / KStreamWindowReduce to not use {{fetch}}, but just as multiple {{get}} calls on the underlying segments, one for each affected window range.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)