DGS-22304: Refactor schema registry references from KafkaSchemaRegist…

[akhileshm1]

…ry to SchemaRegistry

What

Use SchemaRegistry instead of KafkaSchemaRegistry where applicable.

Checklist

Please answer the questions with Y, N or N/A if not applicable.

• [N] Contains customer facing changes? Including API/behavior changes
• [N] Is this change gated behind config(s)?
  • List the config(s) needed to be set to enable this change
• [NA] Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required
• [N] Does this change require modifying existing system tests or adding new system tests?
  • If so, include tracking information for the system test changes
• [N] Must this be released together with other change(s), either in this repo or another one?
  • If so, please include the link(s) to the changes that must be released together

References

JIRA:

Test & Review

Open questions / Follow-ups

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[sonarqube-confluent]

• 67.20% Coverage on New Code (is less than 80.00%)

Analysis Details

8 Issues

• 0 Bugs
• 0 Vulnerabilities
• 8 Code Smells

Coverage and Duplications

• 67.20% Coverage (74.10% Estimated after merge)
• No duplication information (2.00% Estimated after merge)

Project ID: schema-registry

View in SonarQube

[zhaochun-ma]

why SchemaRegistry needs these 2 field? it looks more like common consts

[zhaochun-ma]

not sure why this need to be a interface method

[zhaochun-ma]

The interface has grown quite large (60+ methods) by porting methods from KafkaSchemaRegistry into this interface, and covers multiple concerns:

• Data CRUD operations
• Caching operations (e.g., clear cache methods)
• Multi-tenancy
• Leader election
• Forwarding operations (methods ending with OrForward)
• Extension hooks (handlers, custom handlers)

Have we thought about how this interface will be implemented with RM integration? It might be worth clarifying whether it makes sense to port all of these methods here, or if some should remain separate, or introduce some sub-interfaces for separation of concern

FYI, getMetadataEncoder() method is only used in tests

so does myIdentity()