[
https://issues.apache.org/jira/browse/KAFKA-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049565#comment-17049565
]
Paul Snively commented on KAFKA-9636:
-------------------------------------
I just updated the archive with a more sensible implementation of the generator
for the `join` that's much more readable, and the issue remains. I've
deliberately striven to:
# Limit the number of `KTable`s joined to 2.
# Ensure that the `reduceLeft` I use to actually build the `join`s then
reduces (no pun intended) to just the `join` itself.
I think this new archive makes point #2 significantly clearer.
So my claim is that it's now clear there isn't an error in the test code itself
(or at least, if there is, it probably points to a lack of clarity in the
documentation around how to use `TopologyTestDriver`).
> Simple join of two KTables fails
> --------------------------------
>
> Key: KAFKA-9636
> URL: https://issues.apache.org/jira/browse/KAFKA-9636
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.4.1
> Reporter: Paul Snively
> Priority: Major
> Attachments: merge_issue.zip, merge_issue.zip
>
>
> Attempting to join two KTables yields a `Topology` that, when tested with
> `TopologyTestDriver` by adding records to the two `TestInputTopic`s, results
> in an empty `TestOutputTopic`.
> I'm attaching a very small reproduction. The code is in Scala. The project is
> therefore an "sbt" project. You can reproduce the results from your shell
> with `sbt test`. The failure output will include the `describe` of the
> `Topology` in question.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
