Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Integration
Backwards Compatibility:
Fully Compatible
Linked BF Score:
200
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

This [PR](https://github.com/10gen/mongo/pull/47621) added a 2dsphereIndexVersion v4. It is not possible to downgrade FCV from 8.3 to 8.0 in the presence of v4 indexes. The FCV upgrade/downgrade in the background tests are flaky after this change depending on when the downgrade hits in comparison to the rest of the test. This PR attempts to find all jstests that create 2dsphere indexes and pin them to v3 in FCV upgrade downgrade scenarios. I used Cursor to help aid in these modifications.

is caused by

SERVER-116179 Return error signatures for known 2dsphere index issues in validation response

Closed

is related to

SERVER-120864 Pin 2dsphereIndexVersion to v3 in geo_parse_err.js

Closed

SERVER-120932 Pin 2dsphereIndexVersion to v3 in timeseries 2dsphere tests

Closed

related to

SERVER-121126 Pin 2dsphere index version in clustered_collection_creation test

In Code Review

SERVER-121192 Pin 2dsphereIndexVersion to v3 in timeseries_special_indexes_metadata

In Code Review

SERVER-120418 Pin 2dsphere index version in timeseries test

Closed

(1 related to)

Assignee:: Finley Lau
Reporter:: Finley Lau
Participants:: Finley Lau, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Feb 06 2026 10:01:34 PM UTC
Updated:: Mar 09 2026 01:44:14 PM UTC
Resolved:: Feb 10 2026 10:32:14 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates