[ 
https://issues.apache.org/jira/browse/KAFKA-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058870#comment-17058870
 ] 

Paul Snively commented on KAFKA-9636:
-------------------------------------

John,

Thanks for digging into this so thoroughly.

While I agree that your analysis looks like what it looks like :), the 
challenge I have is this.

Here's the SerDe code:

 
{{implicit val jsonSerde = fromFn(}}
{{  (json: Json) => {}}
{{    Pickle.intoBytes(json).array}}
{{  },}}
{{  (data: Array[Byte]) => {}}
{{    Option(Unpickle[Json].fromBytes(ByteBuffer.wrap(data)))}}
{{  }}}
{{)}}
 
Of course, this just pushes the question off to the implementation of the 
BooPickle codec. But the other test in the project, CircePicklingSpec, tests 
that. From your shell, you can say {{`sbt 'testOnly 
com.compstak.bottleneck.CircePicklingSpec'`}} and see that the {{`Json`}} 
to/from {{`ByteBuffer`}} code works correctly.
 
So I'm afraid I'm still stuck: I don't know how you can be seeing what you're 
seeing, based on the BooPickle codec test and the triviality of the Kafka SerDe.
 

> 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)

Reply via email to