Closed tylerbrandt closed 6 months ago
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
We're using 0.10.2 but it looks like it is probably still an issue in the head of the repo, based on the way the GRPC code works by importing using grpc.protos
which uses importlib
under the hood and that isn't "isolated" in any way.
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
This issue was closed because it has been inactive for 30 days since being marked as stale.
Describe the bug In our system (RedPanda) we have one Schema Registry entity per topic, and many of those registry entities define a protobuf
message
with the same packagemodels
and nameRawEvent
. Additionally, we use the Confluent topic naming strategy in order to allow for easy changes in the future to different topic schemas without having to worry about changes to the schema in one topic affecting the other topics in the future. This works fine in RedPanda because those message are defined only in the context of the individual schema. However, when we ingest this into Datahub, we get the errorduplicate symbol 'models.RawEvent'
(see stack trace below).To Reproduce
SubjectNameStrategy
set toTopicNameStrategy
A
andB
A-values
andB-values
schemas with identical contents (critically, package and message names)Expected behavior Should ingest successfully, since the type namespace is the topic, and there is no collision within a given topic.
Screenshots N/A
Desktop (please complete the following information): N/A
Additional context This problem probably exists for Avro as well, but we haven't tested it.