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 2017/05/26 15:41:04 UTC

[jira] [Updated] (KAFKA-4729) Stores for kstream-kstream join cannot be in-memory

     [ https://issues.apache.org/jira/browse/KAFKA-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eno Thereska updated KAFKA-4729:
--------------------------------
    Fix Version/s:     (was: 0.11.0.0)
                   0.11.1.0

> Stores for kstream-kstream join cannot be in-memory
> ---------------------------------------------------
>
>                 Key: KAFKA-4729
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4729
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 0.10.2.0
>            Reporter: Eno Thereska
>             Fix For: 0.11.1.0
>
>
> Whereas we can specify in the DSL that stores used for aggregates can be RocksDb-based on in-memory, we cannot do that for stores used for KStream-KStream joins. E.g., the join() methon in KStreamImpl.java creates two state stores and the user does not have the option of having them be in-memory:
> StateStoreSupplier thisWindow =
>                 createWindowedStateStore(windows, keySerde, lhsValueSerde, joinThisName + "-store");
>             StateStoreSupplier otherWindow =
>                 createWindowedStateStore(windows, keySerde, otherValueSerde, joinOtherName + "-store");
> Part of the problem is that for joins, stores are not exposed to the user. We might want to rethink that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)