[
https://issues.apache.org/jira/browse/KAFKA-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681546#comment-16681546
]
Manikumar commented on KAFKA-7080:
----------------------------------
[~vvcephei] [~guozhang] Can we create a separate JIRA for the part that was
fixed in 2.0 branch. This will help us to track the changes for 2.0.1 release.
> WindowStoreBuilder incorrectly initializes CachingWindowStore
> -------------------------------------------------------------
>
> Key: KAFKA-7080
> URL: https://issues.apache.org/jira/browse/KAFKA-7080
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.0, 1.0.1, 1.1.0, 2.0.0
> Reporter: John Roesler
> Assignee: John Roesler
> Priority: Major
> Fix For: 2.1.0
>
>
> When caching is enabled on the WindowStoreBuilder, it creates a
> CachingWindowStore. However, it incorrectly passes storeSupplier.segments()
> (the number of segments) to the segmentInterval argument.
>
> The impact is low, since any valid number of segments is also a valid segment
> size, but it likely results in much smaller segments than intended. For
> example, the segments may be sized 3ms instead of 60,000ms.
>
> Ideally the WindowBytesStoreSupplier interface would allow suppliers to
> advertise their segment size instead of segment count. I plan to create a KIP
> to propose this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
