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

KSQL-12194, KSQL-12195 | Classify MissingSchemaException and RecordTooLargeException as user errors. #10361

Open
wants to merge 2 commits into
base: 7.6.x
Choose a base branch
from

Conversation

pbadani
Copy link
Member

@pbadani pbadani commented Jun 10, 2024

Description

Classify MissingSchemaException and RecordTooLargeException as user errors.

Testing done

Describe the testing strategy. Unit and integration tests are expected for any behavior changes.

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 #")
  • Do these changes have compatibility implications for rollback? If so, ensure that the ksql command version is bumped.

@pbadani pbadani requested a review from a team as a code owner June 10, 2024 10:11
@pbadani pbadani changed the title Pbadani/ksql 12194 ksql 12194 KSQL-12194, KSQL-12194 | Classify MissingSchemaException and RecordTooLargeException as user errors. Jun 10, 2024
@pbadani pbadani force-pushed the pbadani/KSQL-12194-KSQL-12194 branch from 9b93fd1 to d754960 Compare June 24, 2024 04:58
@pbadani pbadani changed the title KSQL-12194, KSQL-12194 | Classify MissingSchemaException and RecordTooLargeException as user errors. KSQL-12194, KSQL-12195 | Classify MissingSchemaException and RecordTooLargeException as user errors. Jun 26, 2024
@@ -46,8 +46,10 @@ public final class SchemaRegistryUtil {

@VisibleForTesting
public static final int SUBJECT_NOT_FOUND_ERROR_CODE = 40401;
public static final int SCHEMA_NOT_FOUND_ERROR_CODE = 40403;
Copy link
Member

Choose a reason for hiding this comment

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

Curious question how was the code 40403 determined?

Copy link
Member Author

Choose a reason for hiding this comment

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

The error codes are from the SR code repo

Copy link
Member

@VedarthConfluent VedarthConfluent left a comment

Choose a reason for hiding this comment

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

lgtm, a couple of nit comments

@@ -131,7 +131,7 @@
<wiremock.version>2.24.0</wiremock.version>
<clearspring-analytics.version>2.9.5</clearspring-analytics.version>
<icu.version>67.1</icu.version>
<vertx.version>4.4.6</vertx.version>
<vertx.version>4.4.8</vertx.version>
Copy link
Member

Choose a reason for hiding this comment

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

Why is this change required?

Copy link
Member Author

Choose a reason for hiding this comment

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

that is a mistake, I will revert it.

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