Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Storage Execution
Operating System:
ALL
Linked BF Score:
34

The createIndexes command doesn't specify a type for the "bits" field that is part of the index spec - though there is a struct type "NewIndexSpec" that does define a type for the bits field, the createIndexes command does not use it. However, the listIndexes command does define the "bits" field as type safeInt. This can lead to a problem during any collection cloning phase (we saw an error during Tenant Migrations, but it could happen during initial sync as well), because the node that is cloning indexes typically runs the listIndexes command to learn what indexes it should create.

is related to

SERVER-74305 APIStrict validation is not performed for fields in 'indexes' array in createIndex command

Backlog

SERVER-97084 Validate in createIndex that options for 2dsphere, text, etc. indexes are only used with matching index types

Backlog

SERVER-69750 For certain index options, $listCatalog output could have inconsistent data type as $listIndexes

Closed

SERVER-73858 Inconsistent error handling in singe-phase index builds during oplog application

Closed

related to

SERVER-89210 Chunk migration can unnecessarily fail due to inconsistency between listIndexes and local catalog

In Progress

SERVER-77828 listIndexes should report expireAfterSeconds as a float

Closed

SERVER-73874 clean up geo_small_large.js and initial_sync_index_conflict.js

Closed

(2 related to)

Assignee:: [DO NOT USE] Backlog - Storage Execution Team

Reporter:: Janna Golden

Participants:: [DO NOT USE] Backlog - Storage Execution Team, Benety Goh, Janna Golden

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: Jan 30 2023 03:55:46 PM UTC

Updated:: Nov 13 2024 04:36:38 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates