Best practices for versioning topics #1437
-
|
I am wondering what the general state of versioning a topic is? At the moment, the best I can come up with is to mangle the version number or version-id into the channel topic field. Is it possible to have multiple Channel records sharing the same topic but with different id's? One per version? Is this normal? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Perhaps we set a value in the metadata field of the channel record for the version? |
Beta Was this translation helpful? Give feedback.
-
|
Yes it is valid, although not terribly common, to have multiple channels with the same topic but different versions. Since the schemas are included in mcap, readers are able to correctly deserialize data according to the channel's schema. What problem are you trying to solve by including a version id? |
Beta Was this translation helpful? Give feedback.
-
|
Trying to allow merging of mcaps from several devices which may not have compatible serialization across versioned topics. Also we want to allow for reading and processing of older data captures, where the data format for the topics differs from the current one, for evals going forward. Good to know we can just make several channels for the same topic and use metadata to report the version. |
Beta Was this translation helpful? Give feedback.
Yes it is valid, although not terribly common, to have multiple channels with the same topic but different versions. Since the schemas are included in mcap, readers are able to correctly deserialize data according to the channel's schema. What problem are you trying to solve by including a version id?