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

Error message needs line breaks #7205

Closed
rmoff opened this issue Mar 11, 2021 · 0 comments
Closed

Error message needs line breaks #7205

rmoff opened this issue Mar 11, 2021 · 0 comments
Assignees
Labels
bug core-infra Issues owned by the ksqlDB Core Infra team fix-it-week P1 Slightly lower priority to P0 ;) round-robin

Comments

@rmoff
Copy link
Contributor

rmoff commented Mar 11, 2021

c.f. #7204

This error message:

Schema for message keys on topic FOO2 does not exist in the Schema Registry.Subject: FOO2-key
Possible causes include:
- The topic itself does not exist       -> Use SHOW TOPICS; to check
- Messages on the topic are not serialized using a format Schema Registry supports      -> Use PRINT 'FOO2' FROM BEGINNING; to verify
- Messages on the topic have not been serialized using a Confluent Schema Registry supported serializer -> See https://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html
- The schema is registered on a different instance of the Schema Registry       -> Use the REST API to list available subjects  https://docs.confluent.io/current/schema-registry/docs/api.html#get--subjects
- You do not have permissions to access the Schema Registry.Subject: FOO2-key   -> See https://docs.confluent.io/current/schema-registry/docs/security.html

Should be formatted for better readability as:

Schema for message keys on topic FOO2 does not exist in the Schema Registry.Subject: FOO2-key
Possible causes include:
- The topic itself does not exist
  -> Use SHOW TOPICS; to check
- Messages on the topic are not serialized using a format Schema Registry supports
  -> Use PRINT 'FOO2' FROM BEGINNING; to verify
- Messages on the topic have not been serialized using a Confluent Schema Registry supported serializer
 -> See https://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html
- The schema is registered on a different instance of the Schema Registry
  -> Use the REST API to list available subjects  https://docs.confluent.io/current/schema-registry/docs/api.html#get--subjects
- You do not have permissions to access the Schema Registry.Subject: FOO2-key
  -> See https://docs.confluent.io/current/schema-registry/docs/security.html
@agavra agavra added core-infra Issues owned by the ksqlDB Core Infra team round-robin labels Mar 12, 2021
@rodesai rodesai added P1 Slightly lower priority to P0 ;) fix-it-week and removed needs-triage labels Mar 17, 2021
@cadonna cadonna self-assigned this Mar 17, 2021
cadonna added a commit to cadonna/ksql that referenced this issue Mar 31, 2021
Adds line breaks to the error message when a schema is not found
as described in issue confluentinc#7205.
cadonna added a commit that referenced this issue Apr 1, 2021
Adds line breaks to the error message when a schema is not found
as described in issue #7205.
@cadonna cadonna closed this as completed Apr 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug core-infra Issues owned by the ksqlDB Core Infra team fix-it-week P1 Slightly lower priority to P0 ;) round-robin
Projects
None yet
Development

No branches or pull requests

4 participants