[
https://issues.apache.org/jira/browse/KAFKA-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060302#comment-17060302
]
John Roesler commented on KAFKA-9636:
-------------------------------------
Thanks, [~psnively] !
That's a good idea to add a Scala shim for TopologyTestDriver, since the serdes
could be inferred there as well.
I don't think there's anything we can do about ByteBuffer. It's intended to be
a high-performance API that eschews a lot of the memory safety we're used to
dealing with in JVM code, and the unfortunate downside is that there are some
pitfalls. I've also fallen victim to the same sharp edge in the past with the
`.array()` method. Unfortunately, the Java standard library is outside of our
control.
I'm really glad to hear that the feature seems to work, and again, I'm sorry
for the bugs that slipped through the initial release.
It doesn't really fundamentally address the ByteBuffer thing, but I did get an
idea while digging into this issue that we could completely avoid deserializing
and having to re-serialize in some of the internal code, so I may re-work the
internals at some point to make it more efficient.
Anyway, it sounds like this Jira issue can be resolved; does that sound right
to you?
Thanks,
-John
> 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
> Assignee: John Roesler
> Priority: Major
> Attachments: 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)
