[SERVER-79514] Make value comparison consistent in MatchExpression Created: 31/Jul/23 Updated: 28/Nov/23 Resolved: 28/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alexander Ignatyev | Assignee: | Alexander Ignatyev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
equivalent() function should compare BSONElements consistently in comparison and $in operators. |
| Comments |
| Comment by Alexander Ignatyev [ 28/Nov/23 ] | |||||
|
Minor backward incompatible change. Partial filter expression used not to be validated using provided collation as a result, it was possible to create two equivalent indexes:
However, only the first index index0 will be used to answer queries like
index1 would be never used. After the change the second index1 will be prevented from creating with the following error: MongoServerError: Index already exists with a different name: index0 Nothing changed for databases with existing duplicating partial indexes, the indexes will be kept and only the first created index will be used to serve the queries as it was before. | |||||
| Comment by Githook User [ 27/Nov/23 ] | |||||
|
Author: {'name': 'Alexander Ignatyev', 'email': 'alexander.ignatyev@mongodb.com', 'username': 'aligusnet'}Message: Use the collator to compare values of comparison match expressions. |