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

fix: improve error handling of invalid Avro identifier #6239

Merged
merged 2 commits into from
Sep 17, 2020

Conversation

big-andy-coates
Copy link
Contributor

Description

fixes issue where using a column name in ksqlDB that was incompatible with Avro, e.g. one that starts with a numeric, either wasn't detected at the time the statement was issued (in the case of C* statements), or returned a ambiguous error message (in the case of C*AS statements).

Testing done

Usual

Reviewer checklist

  • Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
  • Ensure relevant issues are linked (description should include text like "Fixes #")

fixes issue where using a column name in ksqlDB that was incompatible with Avro, e.g. one that starts with a numeric, either wasn't detected at the time the statement was issued (in the case of C* statements), or returned a ambiguous error message (in the case of C*AS statements).
@big-andy-coates big-andy-coates requested a review from a team as a code owner September 16, 2020 20:12
@big-andy-coates big-andy-coates changed the title fix: improve error message on invalid Avro identifier fix: improve error handling of invalid Avro identifier Sep 16, 2020
Copy link
Contributor

@vcrfxia vcrfxia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM -- one nit inline.

@big-andy-coates big-andy-coates merged commit 8dd3942 into confluentinc:master Sep 17, 2020
@big-andy-coates big-andy-coates deleted the invalid_avro branch September 17, 2020 09:26
@big-andy-coates big-andy-coates added this to the 0.13.0 milestone Sep 17, 2020
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

Successfully merging this pull request may close these issues.

2 participants