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

Make sure Schemaregistry uses the same code for building transformationchains (during validation) than factcast itself. #1104

Closed
uweschaefer opened this issue Nov 27, 2020 · 0 comments · Fixed by #1404
Labels
bug Something isn't working
Milestone

Comments

@uweschaefer
Copy link
Member

No description provided.

@uweschaefer uweschaefer added the bug Something isn't working label Nov 27, 2020
@uweschaefer uweschaefer added this to the 0.3.7 milestone Nov 27, 2020
@uweschaefer uweschaefer changed the title Make sure Schemaregistry uses the same code (building transformationchains) than factcast itself. Make sure Schemaregistry uses the same code for building transformationchains (during validation) than factcast itself. Nov 27, 2020
otbe added a commit that referenced this issue Jul 1, 2021
updated micronaut
introduced integration test
otbe added a commit that referenced this issue Jul 1, 2021
@uweschaefer uweschaefer linked a pull request Jul 2, 2021 that will close this issue
otbe added a commit that referenced this issue Jul 2, 2021
# Conflicts:
#	factcast-schema-registry-cli/pom.xml
otbe added a commit that referenced this issue Jul 2, 2021
uweschaefer added a commit that referenced this issue Jul 12, 2021
uweschaefer added a commit that referenced this issue Jul 23, 2021
uweschaefer added a commit that referenced this issue Jul 23, 2021
#1104 Use Transformer (pgsql) for schema-registry cli
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant