GitHub user spetz edited a comment on the discussion: Iggy improvements for
current & future use-cases
One more idea, regarding **Additional flags in message header**. Let's align it
to `u64` and add a new field called `schema` being `u16` or `u32` (maybe this
one actually), that could be used for schema registry purposes, uniquely
identifying the particular message schema (if used at all + if there's a need
for validation). The remaining bytes will be reserved fields in case of future
usage.
```rust
pub struct IggyMessageHeader {
pub checksum: u64,
pub id: u128,
pub offset: u64,
pub timestamp: u64,
pub origin_timestamp: u64,
pub user_headers_length: u32,
pub payload_length: u32,
pub format: u8, // Optional serialization format
pub schema: u32, // Optional message schema ID
pub reserved: [u8; 3], // Remaining 24 bits
}
```
GitHub link:
https://github.com/apache/iggy/discussions/2554#discussioncomment-15467851
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
