[SERVER-60607] improve handling of large/NaN values for geo index version Created: 11/Oct/21  Updated: 29/Oct/23  Resolved: 12/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0, 4.4.16, 4.2.22, 5.0.11

Type: Bug Priority: Critical - P2
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-61321 Improve handling of large/NaN values ... Closed
is related to SERVER-56676 improve handling of large/NaN values ... Closed
is related to SERVER-58067 Support 2dsphere indexes on time-seri... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0, v4.4, v4.2
Sprint: Execution Team 2021-10-18
Participants:
Linked BF Score: 58

 Description   

S2AccessMethod::fixSpec() checks the geo index version to ensure it is one of the enumerated values defined in S2IndexVersion. It retrieves the geo index version using BSONElement::numberLong() which does not handle NaN or large values very well.



 Comments   
Comment by Githook User [ 27/Jul/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-60607 S2AccessMethod handles NaN/out of range values when extracting geo index version

(cherry picked from commit 00aa22ab28eca149b203636887df3f425662889c)
Branch: v4.2
https://github.com/mongodb/mongo/commit/0feb08f2081f04417e88dc1baaf486f675edeeb0

Comment by Githook User [ 27/Jul/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-60607 S2AccessMethod handles NaN/out of range values when extracting geo index version

(cherry picked from commit 00aa22ab28eca149b203636887df3f425662889c)
Branch: v4.4
https://github.com/mongodb/mongo/commit/ad3dc99f3c5b7e61847d81c576282d5f2e217778

Comment by Githook User [ 26/Jul/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-60607 S2AccessMethod handles NaN/out of range values when extracting geo index version

(cherry picked from commit 00aa22ab28eca149b203636887df3f425662889c)
Branch: v5.0
https://github.com/mongodb/mongo/commit/ea9e905235d9df7779a5532c58c1cb5a7e2597aa

Comment by Githook User [ 12/Oct/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-60607 S2BucketAccessMethod handles NaN/out of range values when extracting geo index version
Branch: master
https://github.com/mongodb/mongo/commit/b7d6e685c210249607923eee2669cf0a947f556c

Comment by Githook User [ 12/Oct/21 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-60607 S2AccessMethod handles NaN/out of range values when extracting geo index version
Branch: master
https://github.com/mongodb/mongo/commit/00aa22ab28eca149b203636887df3f425662889c

Comment by Benety Goh [ 11/Oct/21 ]

A similar issue in a different part of the server codebase was addressed in SERVER-56676.

Generated at Thu Feb 08 05:50:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.