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

Adding new json schemas to configmap does not add schema - must restart coordinator #71

Open
chipmaurer opened this issue Jan 12, 2022 · 0 comments

Comments

@chipmaurer
Copy link
Contributor

My acceptance tests add the TPCH JSON schema files to the pravega schema configmap. Well, they actually replace the JSON schemas that were there, but that's another story.

If there is a new schema in the JSON files, and the pravega connector (and schema registry) don't know about the new schema, you won't see the schema, or the json tables, so you have to delete the coordinator pod. When it restarts, it will see the JSON files, and create the schema in Schema Registry.

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

1 participant