yzhao244 opened a new pull request #434:
URL: https://github.com/apache/incubator-eventmesh/pull/434
<!--
### Contribution Checklist
- Name the pull request in the form "[ISSUE #XXXX] Title of the pull
request",
where *XXXX* should be replaced by the actual issue number.
Skip *[ISSUE #XXXX]* if there is no associated github issue for this
pull request.
- Fill out the template below to describe the changes contributed by the
pull request.
That will give reviewers the context they need to do the review.
- Each pull request should address only one issue.
Please do not mix up code from multiple issues.
- Each commit in the pull request should have a meaningful commit message.
- Once all items of the checklist are addressed, remove the above text and
this checklist,
leaving only the filled out template below.
(The sections below can be removed for hotfixes of typos)
-->
<!--
(If this PR fixes a GitHub issue, please add `Fixes ISSUE#<XXX>`.)
-->
Fixes ISSUE#339.
### Motivation
- Support Schema Registry feature in EventMesh by integrating with
OpenSchema Specifications
*Explain why you want to make the changes and what problem you're trying to
solve.*
- The purpose of this pull request is for introducing Schema Registry as
part of the EventMesh.
The Schema Registry is a central repository with RESTful interfaces for
developers to define and register standard schemas. Addresses the problem of
inconsistent or incompatible data(event) format between event producer and
event consumer.
### Modifications
- Added eventmesh-store-api module which is an abstract layer abstracts the
CRUD capability of the schema registry into this module.
- Added eventmesh-store-h2 module which contains the actual implementation
- Modified eventmesh-runtime which exposes three new subject APIs
(schemaregistry/createSubject, /schemaregistry/readSubjectByName and
/schemaregistry/showAllSubjectNames) via ClientManageController.
### Documentation
- Does this pull request introduce a new feature? yes
- If yes, how is the feature documented? Another follow up issue or PR will
be created for adding the documentation
- If a feature is not applicable for documentation, explain why?
- If a feature is not documented yet in this PR, please create a followup
issue for adding the documentation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
