-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 1.32.2
-
None
-
Environment:Compass Version 1.29.6 (1.29.6)
-
Not Needed
Problem Statement/Rationale
When a single field text index (not compound) is displayed in Compass (Version 1.29.6 (1.29.6)), it shows as being a compound index under its properties. This seems to be due to text indexes having a key definition of key:
{ _fts: 'text', _ftsx: 1 }Steps to Reproduce
Create a single field text index, such as db.myTest.createIndex(
{a:"text"}). View the properties of the index in Compass, and it should show "COMPOUND".
Expected Results
It should not be displayed as a compound index. Text indexes are always sparse, so it should have a property of sparse. That's how it works in the Atlas UI.
Actual Results
It incorrectly shows the single field index as being a compound index
Additional Notes
This varying behavior has caused confusion for users when viewing an index in Compass vs Atlas. Screenshots attached for the same index when viewed in Compass and Atlas.