[SERVER-17658] Upgrade/downgrade support for partial indexes Created: 19/Mar/15  Updated: 07/Jun/17  Resolved: 25/Aug/15

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Storage
Affects Version/s: None
Fix Version/s: 3.1.8

Type: Task Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-19358 Invariant failure during upgrade from... Closed
Related
is related to SERVER-16450 Warn/error if invalid indexes present Closed
is related to SERVER-19347 Generic upgrade/downgrade jstest fram... Closed
Backwards Compatibility: Fully Compatible
Sprint: QuInt 8 08/28/15
Participants:

 Comments   
Comment by Githook User [ 25/Aug/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-17658 Fail to start up with an invalid partial index.

Changed to check that all index specs are OK on startup.
Branch: master
https://github.com/mongodb/mongo/commit/04dbe8b560463211bb54e7adab318ec5a8737624

Comment by J Rassi [ 10/Jul/15 ]

See also linked ticket SERVER-19358. As part of this work, it should be ensured that the server exhibits improved behavior under the test conditions described in that ticket.

Comment by J Rassi [ 10/Apr/15 ]

On further thought, this isn't as simple as reserving a new flag to the mmapv1 data file version, as it has to work for WiredTiger as well.

We may want to couple this with a broader change that introduces strict validation to the index spec object. This would provide a unified way to introduce new backwards-breaking index changes.

Per discussion with Dan/Mathias, we should spec this out in 3.1.3.

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