Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 16 Aug 2016 18:20:20 +0000 (UTC)
From: "Eno Thereska (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12997551.1471345357000.320607.1471371620535@Atlassian.JIRA>
In-Reply-To: <JIRA.12997551.1471345357000@Atlassian.JIRA>
References: <JIRA.12997551.1471345357000@Atlassian.JIRA> <JIRA.12997551.1471345357139@arcas>
Subject: [jira] [Reopened] (KAFKA-4045) Investigate feasibility of hooking
 into RocksDb's cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 16 Aug 2016 18:20:22 -0000


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

Eno Thereska reopened KAFKA-4045:
---------------------------------

Reopening since it's worth checking with the RocksDb community on future plans around this.

> 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)