-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Index Maintenance
-
None
-
ALL
-
After upgrading to mongo 4.2 and running an "install" script on an application, I started getting some errors in regards to "Index with name: INDEX_NAME already exists with a different name"
The problem appears to be that related to index names (at some point in mongo's past, automatic index naming used an underscore to delineate field names, for example "a_b_1" instead of "a.b_1" for an index created on {'a.b': 1} and the background flag.
This isn't a big deal to me, I will just manually recreate indexes, but I did think it was a problem worth mentioning in case it ties to something else.
- is related to
-
SERVER-33149 createIndexes fails to report an error when index is not created with the specified name
- Closed