You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to use a proto file with additional dependencies, the way this is being handled by the Confluent schema registry is to create a subject per external dependency and resolve it when it's being queried. If I try to do the same using the Apicurio schema registry, the write works well, but when I try to deserialize the data, it fails because it can not resolve one type. I couldn't find a way to do write the external dependencies to the schema registry and use them when reading. This was also working fine with the previous version (1.3.1.Final) using the PROTOBUF_FD
The text was updated successfully, but these errors were encountered:
@EricWittmann , do you have a rough ETA on when this may be implemented? I am currently working on a large project where we use Protobuf to define events posted to our Kafka infrastructure. All the Protobuf schemas are using package and import for code re-usability and we have been looking into adopting the Apicurio Registry. This is a must-have feature for us to proceed.
I was trying to use a proto file with additional dependencies, the way this is being handled by the Confluent schema registry is to create a subject per external dependency and resolve it when it's being queried. If I try to do the same using the Apicurio schema registry, the write works well, but when I try to deserialize the data, it fails because it can not resolve one type. I couldn't find a way to do write the external dependencies to the schema registry and use them when reading. This was also working fine with the previous version (1.3.1.Final) using the PROTOBUF_FD
The text was updated successfully, but these errors were encountered: