[DOCS-9933] Explain that regex is unable to take advantage of indexes that use collation Created: 24/Feb/17 Updated: 30/Oct/23 Resolved: 17/Oct/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dmitry Ryabtsev | Assignee: | Stennie Steneker (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 6 years, 17 weeks, 1 day ago | ||||||||||||
| Description |
|
With the release of 3.4 we introduced collations. Among other benefits, that allows MongoDB users to create case-insensitive indexes. Some of these users (not unreasonably) expect that $regex case insensitive queries should be able take advantage of such indexes. Unfortunately that is not the case - the regex implementation is not collation-aware and is unable to utilize case-insensitive indexes. We should have this explained somewhere in the documentation about $regex index use. |
| Comments |
| Comment by Githook User [ 17/Oct/17 ] |
|
Author: {'email': 'stennie@cpan.org', 'name': 'Stephen Steneker', 'username': 'stennie'}Message: |
| Comment by Githook User [ 17/Oct/17 ] |
|
Author: {'email': 'stennie@cpan.org', 'name': 'Stephen Steneker', 'username': 'stennie'}Message: |