Fixed Issues in Schema Registry

Review the list of Schema Registry issues that are resolved in Cloudera Runtime 7.2.14.

CDPD-32192: First start failed for SR, with oracle DB, migration failed at CREATE TABLE "atlas_events"

Fixed v009__create_registry_audit.sql to have create index refer to the lower case "atlas_events" object (the table).

Made the script re-runnable since the table was already created where the script had already run.

CDPD-31907: Schema Registry REST API endpoint does not show SchemaBranches

Schema Registry’s /api/v1/schemaregistry/schemas/aggregated REST API endpoint shows SchemaBranches without SchemaVersions.

CDPD-30996: SR does not create new SchemaMetadata with given ID

In DefaultSchemaRegistry class, addSchemaMetadata (Supplier<Long> id, SchemaMetadata schemaMetadata, boolean throwErrorIfExists) does not look for the given ID, but the next available ID.

CDPD-29700: Hide Compatibility list in the website

When the schema type is JSON, then the Compatibility field will be hidden in the website.

CDPD-29663: Error while connecting topic with schema in Atlas

When Schema Registry tries to make a relationship in Atlas between a schema and a non-existent corresponding topic, an error occurs.

CDPQE-11299: Importing schemas in Confluent format might fail

Fixed the issue where importing from the Confluent Schema Registry fails intermittently.