-
Notifications
You must be signed in to change notification settings - Fork 574
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
Schema registry protobuf compatibility issue #3633
Comments
There''s a couple of issues here:
I have a proof of concept working on a branch. I will tidy it up and add tests. |
Requires fix for: redpanda-data/redpanda#3633 Signed-off-by: Ben Pope <ben@vectorized.io>
Support decoding a protobuf FileDescriptor as encoded protobuf. Fix redpanda-data#3633 Signed-off-by: Ben Pope <ben@vectorized.io>
Support decoding a protobuf FileDescriptor as encoded protobuf. Fix redpanda-data#3633 Signed-off-by: Ben Pope <ben@vectorized.io> (cherry picked from commit d74b9e5)
Support decoding a protobuf FileDescriptor as encoded protobuf. Fix redpanda-data#3633 Signed-off-by: Ben Pope <ben@vectorized.io>
Testing with v21.11.4-beta1, I am still getting the same issue. I would like to send a repro but that requires sharing the whole Java program, unfortunately. |
This is also being replicated on v22.1.5 with the same behaviour as described in the issue. Some details after debugging this that may help. We noticed that despite pushing a valid |
Hi @JuxhinDB - do you think you could send me a repro? Perhaps the schema would be useful. If it's sensitive you can email me or DM in slack: https://redpanda.com/slack |
Version & Environment
Redpanda version: 21.11.3 (inside of Docker)
What went wrong?
When switching from the cp-schema-registry to the redpanda one, our software encounters some issues. The full log is below but I believe there is a hint in this part:
"of type AVRO", but we only use protobuf in the software.
What should have happened instead?
Be compatible with cp-schema-registry.
How to reproduce the issue?
I don't have a minimal repro yet. If the issue is not obvious on your side, I'm happy to try and produce one for you.
Additional information
CLICK ME - full log
The text was updated successfully, but these errors were encountered: