[SERVER-26659] Only apply stricter index key pattern validation to v:2 indexes Created: 17/Oct/16 Updated: 25/Jun/19 Resolved: 20/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.4.0-rc0 |
| Fix Version/s: | 3.4.0-rc2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Asya Kamsky | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Steps To Reproduce: | Create an index using value like "true" instead of 1 or -1 in index spec. Start up 3.3/3.4 on it. |
||||||||||||||||||||||||
| Sprint: | Query 2016-10-31 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
In Original descriptionRelated to change made in
|
| Comments |
| Comment by Githook User [ 20/Oct/16 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: This now follows the same rules which we will use in 3.4 for |
| Comment by Daniel Pasette (Inactive) [ 19/Oct/16 ] |
|
david.storch That seems like the only sane approach |
| Comment by David Storch [ 19/Oct/16 ] |
|
We can avoid the problem altogether by only applying the new validation to v:2 indexes. This will ensure that new indexes on fully upgraded 3.4 systems always obey the new validation rules, but also that the system can fully tolerate v:1 index specs created on old versions. |
| Comment by Asya Kamsky [ 17/Oct/16 ] |
|
Also
I assume that'll be the same error message that needs to be more clear. |