mongodb / mongodb/specifications
DriverBench full_bson.json uses legacy binary type:
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 409
- Forks
- 248
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 7
Description
full_bson.json includes the following segment:
"BOQAeydE": {
"$binary": "RWNVVkhUUmVsWEhzcnhxV25WdnVQTWFERUJMRFRrYmlOVUFGYmh3QWZzRGtTRkVHT1lrTWFKR2twUUFIZVVGWkJ1Y1RlYlpNTGF2VG51Vk8=",
"$type": "00"
},
This is the legacy binary format, and should look something like:
"Binary": {
"$binary": {
"base64": "RWNVVkhUUmVsWEhzcnhxV25WdnVQTWFERUJMRFRrYmlOVUFGYmh3QWZzRGtTRkVHT1lrTWFKR2twUUFIZVVGWkJ1Y1RlYlpNTGF2VG51Vk8=",
"subType": "03"
}
},
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the full_bson.json fixture and compare the reported segment with the BSON extended JSON format shown in the issue. Update the binary value to the object form with base64 and subType fields, then verify that the fixture remains valid and uses the non-legacy representation.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100