Skip to content
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

Missing KEY_FORMAT parameter #805

Closed
maver1ck opened this issue Feb 27, 2018 · 5 comments
Closed

Missing KEY_FORMAT parameter #805

maver1ck opened this issue Feb 27, 2018 · 5 comments

Comments

@maver1ck
Copy link

Hi,
I'm using KSQL for querying data where both key and value are serialized with Avro.
How can I specify the format for KEY ?

@apurvam
Copy link
Contributor

apurvam commented Feb 27, 2018

KSQL only accepts avro values. The keys themselves are always interpreted as strings. Do you have a use case for accessing fields within an avro encoded key?

@maver1ck
Copy link
Author

No. I wanted to group by key. And don't know how. (whole key so it can by string)

@apurvam
Copy link
Contributor

apurvam commented Feb 28, 2018

Have you seen our documentation on https://github.com/confluentinc/ksql? It has plenty of examples for grouping by key.

@rmoff
Copy link
Member

rmoff commented Mar 23, 2018

@maver1ck whilst there's no support for Avro keys currently, you can use KSQL to re-key a topic (PARTITION BY). The resulting topic will have String keys and can then be correctly used for joining, grouping, etc. This blog posts demonstrates this feature in action: https://www.confluent.io/blog/ksql-in-action-real-time-streaming-etl-from-oracle-transactional-data

@rmoff rmoff closed this as completed Jun 21, 2018
@rmoff
Copy link
Member

rmoff commented Jun 21, 2018

Track support for avro keys in #824

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants