[COMPASS-5726] Allow displaying bson binary data where the payload is invalid for the subtype Created: 12/Apr/22 Updated: 29/Oct/23 Resolved: 13/Apr/22 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | CRUD |
| Affects Version/s: | 1.31.1 |
| Fix Version/s: | 1.31.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rhys Howell | Assignee: | Sergey Petushkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Documentation Changes: | Not Needed |
| Sprint: | Iteration Yonkers |
| Description |
|
Reported on github: Example document which errors Compass now:
In previous versions of Compass (using 1.21.2 for reference) we would render binary fields which have invalid payload for the corresponding $type as follows: In current Compass this document results in the crud view failing to render: What's happening is the `payload`, or `$binary`, of the field does not match the 36 character UUID format (UUID is denoted by the `$type` = 4). https://www.mongodb.com/docs/manual/reference/mongodb-extended-json/#mongodb-bsontype-Binary An example document in this format that displays this error is in the `test.all_types` in the Compass Data Sets deployment. |