[SERVER-21804] Change type of pingMs when displayed in shell Created: 09/Dec/15  Updated: 06/Dec/22  Resolved: 03/Dec/21

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: 3.2.0
Fix Version/s: features we're not sure of

Type: Improvement Priority: Major - P3
Reporter: Semen Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: move-stm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File info.txt    
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

I have been added to the replica (MongoDb version 3.0.2) the new members of the replica (new version 3.2.0), after members of the replica with old versions have been removed. Now I see "pingMs" : NumberLong(0) incomprehensible. What could be the problem?



 Comments   
Comment by Brooke Miller [ 03/Dec/21 ]

We've deprecated the mongo shell in favor of the new  mongosh. Unfortunately, we aren't able to pursue improvements to the deprecated shell except in extreme cases, such as critical security fixes. Please start making use of mongosh and let us know if it works for you in this case.

Comment by Kelsey Schubert [ 16/Dec/15 ]

Hi srsd,

In 3.2, we modified the underlying storage type for milliseconds. As a result of this improvement, pingMs is now stored as long instead of a double. Since javascript does not support long, it is displayed as NumberLong(0) in the mongo shell.

For more details on how data types are handled in mongo shell, please see our documentation.

I am marking this ticket as an improvement request to provide a cleaner view of the pingMs value in the mongo shell.

Thank you,
Thomas

Generated at Thu Feb 08 03:58:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.