-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KSQL join does not work if table topic key is Avro serialised #894
Comments
Thanks for looking at this @rmoff. The only part that doesn't make sense to me is that KSQL seems to be able to parse the key correctly:
If the key is serialized avro I would expect it to look like junk on the console. Maybe the junk surrounding "1" just isn't being rendered. |
I'm going to close this. Issue #847 captures the need for better documentation of the restrictions on the KEY. |
Hi Team, |
@entechlog Please read #824 |
Start ksqlserver, start ksql
Create
people
topic implicitly and add a message:enter a value -- note it is a tab character between the key ("1") and the rest of the message
Create
achivement
topic and add a message:enter a value -- note it is a tab character between the key ("1") and the rest of the message
KSQL - define objects and inspect:
Try to join:
Note the
null
fields where it should be values fromperson
TABLEValidate that the data exists on the matching key:
The problem is that KSQL does not support Avro keys. We can actually use KSQL to rekey the topic, using
PARTITION BY ID
:Now let's test the join again…
Happy days :)
So if in the topic that underpins the table used in a join, the key is Avro serialised, the join will not work. The key format must be
STRING
.Related: #824
The text was updated successfully, but these errors were encountered: