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

[Schemas] Use configured schema service in Avro processors #1653

Closed
Tracked by #1560
hariso opened this issue Jun 12, 2024 · 1 comment · Fixed by #1743
Closed
Tracked by #1560

[Schemas] Use configured schema service in Avro processors #1653

hariso opened this issue Jun 12, 2024 · 1 comment · Fixed by #1743
Assignees
Labels
feature New feature or request

Comments

@hariso
Copy link
Contributor

hariso commented Jun 12, 2024

Part of #1560.

With schema support in Conduit, we come to the questions:

  • Should the Avro processors be able to use Conduit's schema service?
  • If yes, how?
@hariso hariso mentioned this issue Jun 12, 2024
17 tasks
@hariso
Copy link
Contributor Author

hariso commented Jun 12, 2024

Comment by @lovromazgon:

Not for this PR, but I'll mention it before I forget. I realized that having a builtin schema registry could create the expectation that the avro.decode and avro.encode processors would be able to use the internal schema registry. It would be a bit strange if we had to configure Conduit to point to a schema registry and then again supply the URL to the processors separately. So ideally the processors should use this service to create and get schemas. Not sure if this was included in the design or not.

#1605 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants