[
https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835784#comment-16835784
]
Andrew commented on KAFKA-8315:
-------------------------------
After a lot of investigation, we think this issue is down to the fact that we
have a left stream with minute-by-minute data and a right topic with daily data.
It is not clear what logic controls the rate at which records are read from
left and right streams, but we believe that the right topic is being read at a
rate such that that it quickly gets too far ahead of the left stream (in terms
of event-time) and therefore the right stream windows are being expired before
the left stream data has been read.
[~vvcephei] What controls the rate that records are read from the left and
right streams? Is there any guarantee that the timestamps for the records in
the left and right streams are kept more-or-less in line with the records from
the right stream?
If not, is there any way we can somehow delay the right stream?
Thanks for your help above.
> Cannot pass Materialized into a join operation - hence cant set retention
> period independent of grace
> -----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-8315
> URL: https://issues.apache.org/jira/browse/KAFKA-8315
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Andrew
> Assignee: John Roesler
> Priority: Major
> Attachments: code.java
>
>
> The documentation says to use `Materialized` not `JoinWindows.until()`
> ([https://kafka.apache.org/22/javadoc/org/apache/kafka/streams/kstream/JoinWindows.html#until-long-]),
> but there is no where to pass a `Materialized` instance to the join
> operation, only to the group operation is supported it seems.
>
> Slack conversation here :
> [https://confluentcommunity.slack.com/archives/C48AHTCUQ/p1556799561287300]
> [Additional]
> From what I understand, the retention period should be independent of the
> grace period, so I think this is more than a documentation fix (see comments
> below)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
