I'm trying to bring in my Confluent Cloud instance to Datahub. Schemas are protobuf in Confluent Schema Registry. Most of our message keys are uuids, the schema for topic key in the registry is:

syntax = "proto3";
package atech.proto.shared;

message Uuid {
  string value = 1;
}

What I'm seeing is its pulling in one topic, then erroring on the second. I think its telling me because of duped shared proto objects:

TypeError: Couldn't build proto file into descriptor pool!
Invalid proto descriptor for file "shared/uuid.proto":
  atech.proto.shared.Uuid.value: "atech.proto.shared.Uuid.value" is already defined in file "atech_app_journey_ape_completed-key.proto".
  atech.proto.shared.Uuid: "atech.proto.shared.Uuid" is already defined in file "atech_app_journey_ape_completed-key.proto".

Seems that I might have hit this this limitation but can't think of a workaround, so not quite sure where to go from here? Any clues?

@helpful-optician-78938 Do you have any guidance for Chris (I know you've worked on this previously)

I could live with that for now, but I couldn't see a config property to turn off the schema stuff

Oh - neither do I. I would definitely expect that to exist. Let me sink with a few folks to understand this a bit better

No worries, thanks for having a look. I'm knocking together a quick python emitter together as a workaround which pulls all the topic names and posts a simple

datasetProperties

aspect for each

okay got it

I hacked this gist together to move the project along for now, plugs the gap in our lineage