-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
v6.1, v6.0
-
Execution Team 2022-12-26
-
34
As an example, if user creates an index and specifies expireAfterSeconds option to be a floating point, like 101.23. The creation would succeed and $listIndexes outputs expireAfterSeconds as an integer 101, since this field is declared to be safeInt in IDL. However $listCatalog would still output expireAfterSeconds as floating point 101.23. This behavior causes issues and confusions to downstream consumers like C2C because the expectation is $listCatalog output is consistent with $listIndexes.
- is related to
-
SERVER-89210 Chunk migration can unnecessarily fail due to inconsistency between listIndexes and local catalog
- Backlog
-
SERVER-62006 Support majority read for _mdb_catalog
- Closed
-
SERVER-64404 improve sharding support $listCatalog aggregation stage
- Closed
- related to
-
SERVER-73442 The type of the "bits" field can differ between createIndexes and listIndexes
- Backlog
-
SERVER-69783 use integral type for TTL index test case in ttl_index_options.js
- Closed
-
SERVER-72129 Document $listCatalog output format for internal use
- Closed