[ https://issues.apache.org/jira/browse/KAFKA-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050440#comment-17050440 ]
Paul Snively commented on KAFKA-9636: ------------------------------------- Hi John! Good catch! I've fixed the "records referring to their own key" issue, and things definitely progress further. I've attached the latest "minimal" test. Unfortunately, they still do go haywire later. I also added a `println` for the pertinent values, I believe, at the pertinent place, and you can clearly see several examples where the correct (in the sense the key field of the record going to `input-topic-1` refers to the key of the record going to `input-topic-2`) records are going to the correct input topics, and then there's more output, meaning those cases have passed. You can also see from the generated record contents that things are usually not failing when ScalaCheck tries its trivial cases, where strings tend to be empty, values tend to be `null`, etc. Of course, I imagine I'm still doing something wrong. But it's clearly progress! Thanks so much! > 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: kafka.tar.xz, merge_issue.zip, 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)