[jira] [Resolved] (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:all-tabpanel ] Eno Thereska resolved KAFKA-4045. - Resolution: Fixed > 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)
[jira] [Resolved] (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:all-tabpanel ] Eno Thereska resolved KAFKA-4045. - Resolution: Fixed Unfortunately hooking into RocksDb is not possible at this time. End of investigation. > 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)
