Adding new json schemas to configmap does not add schema - must restart coordinator #71
Description
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.