[SERVER-5826] Creating an index using a non-existing plugin should be an error not a warning Created: 11/May/12  Updated: 14/May/14  Resolved: 05/Mar/13

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 2.4.0-rc2

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-8638 Allowed to build {<field>:0} index Closed
Related
is related to SERVER-8751 Downgrading 2.4=>2.2 without dropping... Closed
is related to SERVER-11064 Stricter validation of index key patt... Closed
is related to SERVER-8923 Users with {foo:"1"} indexes able to ... Closed
Backwards Compatibility: Minor Change
Operating System: ALL
Participants:

 Description   

Currently just does:

log() << "warning: can't find plugin [" << pluginName << "]" << endl;

This means that typos like this will succeed and silently (excluding the log) do nothing:

db.places.ensureIndex({location:"2D"})

This will be a breaking change for users who mistakenly use string "1" instead of number 1 in their index specs.



 Comments   
Comment by auto [ 05/Mar/13 ]

Author:

{u'date': u'2013-03-01T19:14:00Z', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-5826 prevent building an index with a non-existent plugin
Branch: master
https://github.com/mongodb/mongo/commit/629ed9f2a0bd63fe6640d6497aeee840bd474214

Generated at Thu Feb 08 03:09:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.