What are the best practices of backward/forward compatibility and versioning when defining protocol buffer v3 message types?
Is it recommended to deliver a schema version identifier with the messages (either "envelope" or message itself) in order for the recipient to be able to infer whether to process the message or drop it? I'm planning to deliver messages primarily through Kafka, so it would be possible to include a schema version number in message header. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/ef0028b7-663b-45c5-a403-c2295301ab2e%40googlegroups.com.
