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
Currently the protobuf definitions for the taskbroker are in sentry-protos. However the kafka topic needs to be defined in sentry-kafka-schemas to be created in production, and the topic shouldn't be created with an empty schema.
Options/Ideas:
Have the schemas defined in both places, and try to manually keep them in sync
Move entirely to sentry-kafka-schemas. This will require work in that repo to make that efficient in processing protobuf encoded messages.
Keep the schemas in sentry-protos, and import them into sentry-kafka-schemas. This would also require some work to create that mechanism.
The text was updated successfully, but these errors were encountered:
However the kafka topic needs to be defined in sentry-kafka-schemas to be created in production, and the topic shouldn't be created with an empty schema.
Currently, sentry-kafka-schemas can reference a protobuf struct as a message encoding, and I've linked sentry-protos in so that the validation methods in sentry-kafka-schemas will use the generated protobuf bindings. Which is roughly the flow you mentioned.
Keep the schemas in sentry-protos, and import them into sentry-kafka-schemas. This would also require some work to create that mechanism.
Currently the protobuf definitions for the taskbroker are in
sentry-protos
. However the kafka topic needs to be defined insentry-kafka-schemas
to be created in production, and the topic shouldn't be created with an empty schema.Options/Ideas:
sentry-kafka-schemas
. This will require work in that repo to make that efficient in processing protobuf encoded messages.sentry-protos
, and import them intosentry-kafka-schemas
. This would also require some work to create that mechanism.The text was updated successfully, but these errors were encountered: