[jira] [Commented] (KAFKA-12960) WindowStore and SessionStore do not enforce strict retention time

["Lucas Brutschy (Jira)" <ji...@apache.org>]

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

Lucas Brutschy commented on KAFKA-12960:
----------------------------------------

There is a third PR here: https://github.com/apache/kafka/pull/12756

> WindowStore and SessionStore do not enforce strict retention time
> -----------------------------------------------------------------
>
>                 Key: KAFKA-12960
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12960
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Matthias J. Sax
>            Assignee: Sagar Rao
>            Priority: Major
>             Fix For: 3.4.0
>
>
> WindowedStore and SessionStore do not implement a strict retention time in general. We should consider to make retention time strict: even if we still have some record in the store (due to the segmented implementation), we might want to filter expired records on-read. This might benefit PAPI users.
> Atm, InMemoryWindow store does already enforce a strict retention time.
> As an alternative, we could also inject such a filter in the wrapping `MeteredStore` – this might lift the burden from users who implement a custom state store.
> As an alternative, we could change all DSL operators to verify if data from a state store is already expired or not. It might be better to push this responsibility into the stores though.
> It's especially an issue for stream-stream joins, because the operator relies on the retention time to implement it's grace period.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)