[
https://issues.apache.org/jira/browse/KAFKA-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434073#comment-17434073
]
A. Sophie Blee-Goldman commented on KAFKA-12960:
------------------------------------------------
Oh yeah I agree, I was just saying that it only matters what the underlying
layers because at the moment we only do this check at the innermost layer. If
we move it to the Metered layer then it shouldn't matter whether we have
caching or not since everything goes through that metered layer
(not that it hurts to have additional test coverage of course)
> 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
>
> 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.3.4#803005)
