Convert MSGPACK to BSON
Turn MSGPACK files into BSON. One BSON document with the same keys in order; a top-level list is wrapped under the key items and any other value under value.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop MSGPACK files on the dialor turn it to pick what to do
MessagePack data as a BSON document.Keys keep their order, and values keep their types.
What you get
One BSON file holding a single document. The keys come out in the same order as in the MessagePack input.
Integers, floats, booleans, null, text, nested objects and lists keep their types.
What gets wrapped
A BSON file must be a document, so some inputs are placed under a key. A top-level list is wrapped under the key items. Any other top-level value is wrapped under the key value.
What changes
Dates stay text. Binary values become base64 text. Timestamps become ISO 8601 text in UTC.
Integers beyond the signed 64-bit range become floats. Those values are stored as floats, not as exact integers.
To go the other way, use BSON to MSGPACK.
MSGPACK and BSON.What each format is.
The formats
MessagePack
Binary JSON: the same values as JSON in a compact byte encoding.
- Extensions
- .msgpack .mpk
- MIME type
- application
/msgpack - Kind
- Text and data
BSON
MongoDB's binary document encoding, JSON with dates and binary fields.
- Extensions
- .bson
- MIME type
- application
/bson - Kind
- Text and data
In your code.The same MSGPACK to BSON conversion through the API, for your app or your agent.
$ cv convert report.msgpack report.bson$ cv convert report.msgpack report.bsonQuestions.What people ask about MSGPACK to BSON.
It is wrapped in a document under the key items. A top-level value that is not an object or a list goes under the key value.
No. Binary values become base64 text in the BSON file.
As ISO 8601 text in UTC. They are not stored as BSON date values.
Not beyond the signed 64-bit range. Those integers become floats.