-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.0.0
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
CAR Team 2024-11-25
-
2
The listIndexes command uses different data types for some number fields (e.g. "bits") than what is stored on disk, which can lose precision. The migration recipient currently uses listIndexes to get the indexes the donor has for the collection. This can lead to indexes across shards having slightly different values if the migration would cause the index to be created, or it can lead to unnecessarily failing a migration if an index exists on both shards (because the value for some field but have lost precision and would not compare the same).
- duplicates
-
SERVER-84434 Chunk migration may fail due to indexes having not relevant and invalid index options
- Closed
- is related to
-
SERVER-73442 The type of the "bits" field can differ between createIndexes and listIndexes
- Backlog
-
SERVER-97084 Validate in createIndex that options for 2dsphere, text, etc. indexes are only used with matching index types
- Backlog
-
SERVER-77828 listIndexes should report expireAfterSeconds as a float
- Closed
- related to
-
SERVER-69750 For certain index options, $listCatalog output could have inconsistent data type as $listIndexes
- Closed