You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Damian Guy (JIRA)" <ji...@apache.org> on 2016/08/17 08:29:20 UTC

[jira] [Commented] (KAFKA-4045) Investigate feasibility of hooking into RocksDb's cache

    [ https://issues.apache.org/jira/browse/KAFKA-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424099#comment-15424099 ] 

Damian Guy commented on KAFKA-4045:
-----------------------------------

https://github.com/facebook/rocksdb/issues/1282

> Investigate feasibility of hooking into RocksDb's cache
> -------------------------------------------------------
>
>                 Key: KAFKA-4045
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4045
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: Eno Thereska
>            Assignee: Damian Guy
>             Fix For: 0.10.1.0
>
>
> Ideally we could hook a listener into RockDb's cache so that when entries are flushed or evicted from the cache the listener is called (and can subsequently perform Kafka Streams-specific functions, like forward a record downstream). That way we don't build our own cache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)