[COMPASS-3023] As a user, I want to view timestamp BSON objects similarly to how the command line displays them Created: 27/Jul/18 Updated: 21/Dec/21 Resolved: 21/Dec/21 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | CRUD |
| Affects Version/s: | 1.15.0, 1.28.1 |
| Fix Version/s: | 1.29.4 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Gerald Horn | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Story Points: | 5 |
| Documentation Changes: | Not Needed |
| Description |
|
In the mongo command line, timestamps are displayed as a tuple of two values corresponding to the two 32-bit fields in the timestamp object itself. However, in Compass it is displayed as a single long number (I'm assuming the value that corresponds interpreting the two 32 bit values as 1 64 bit long...) I find the command line view much more usable. So much so that I currently cannot use Compass to help me troubleshoot a bug in our application. Please consider displaying these in a more consumable format. For reference, I've attached a screenshots comparing how the two represent identical documents |
| Comments |
| Comment by Anna Henningsen [ 21/Dec/21 ] |
|
Aligned with mongosh as a 2-field display in |
| Comment by Maurizio Casimirri [ 26/Aug/21 ] |
|
Still applies in 1.28.1, also in json mode the timestamp is represented as an empty object. This may happen with other BSON types too. |