Repository navigation
Preserve typed map keys in MessagePack and binary archives - #756
Merged
liuzicheng1987 merged 1 commit intoOct 25, 2026
Merged
liuzicheng1987 merged 1 commit into
liuzicheng1987 merged 1 commit into
Conversation
Add an optional backend capability for parsing and writing map keys as values. Enable it for MessagePack, cereal, YAS, and Boost.Serialization without a legacy string-key compatibility path. Cover precision, validation, nested maps, wire formats, and truncation; document the change and the existing CBOR DOM limitation.
Contributor
Author
|
Macos failure due to vcpgk hiccup, not a real issue |
Collaborator
|
@Altren thanks |
liuzicheng1987
merged commit Oct 25, 2026
2e6411b
into
munich-data-engineering:main
175 of 176 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Serialize map keys as typed values in MessagePack, cereal, YAS, and Boost.Serialization. This avoids numeric/string conversions and preserves floating-point key precision. Shared map parsing uses explicit map-entry contexts; the unused string-key archive readers are removed.
Compatibility: This intentionally changes the wire format for numeric keys, with no backward-compatibility layer. Other backends, including CBOR, retain their current representation.
Performance: a minor improvement in existing string-key workloads (mostly 1–4% faster)