[
https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837765#comment-16837765
]
Sophie Blee-Goldman commented on KAFKA-8315:
--------------------------------------------
[~the4thamigo_uk] After I directed you to check out RecordQueue I went back to
look over it and filed the ticket John linked: you're right, it actually was
going by partition time rather than by the timestamp of the head record. I've
opened a simple PR with the fix
[here|[https://github.com/apache/kafka/pull/6719]]
That said, I'm not sure this actually affects your use case. If all the data is
in order, partition time should be the same as the head record's timestamp, so
this should only come into play when processing out of order data. In your
example above, partition A would have streamtime = 1 when first choosing the
next record, as it will not have seen the record with timestamp 4 yet.
> 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)
