[
https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838720#comment-16838720
]
John Roesler commented on KAFKA-8315:
-------------------------------------
Hi [~the4thamigo_uk],
Unfortunately, the TopologyTestDriver is going to be insufficient for
exercising the behavior you want, since it processes events synchronously as
soon as you call `pipeInput`, but the problem you're having appears to be with
the logic that chooses records polled from Kafka (which only KafkaStreams does).
I'd suggest, as the fastest way to try and nail this down, actually to pull the
Kafka project down (since we have set up integration tests that actually do use
the brokers and run a "real" KafkaStreams) and modify one of the join
integration tests to reproduce your use case.
This still sounds like a bug to me, even though it might not be the one that
[~ableegoldman] reported.
Regarding the ticket, it'd be better not to split the history of this
investigation, so I recommend just editing the title and description of the
ticket, instead of making a new ticket.
Thanks,
-John
> 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)
