[DOCS-6853] Clarify how case sensitivity affects a prefix regex Created: 19/Dec/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Minor - P4
Reporter: Ian Mercer Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: bite-sized, collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server

Location: https://docs.mongodb.org/v3.0/reference/operator/query/regex/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36
Referrer: https://www.google.com/
Screen Resolution: 1440 x 900
repo: docs
source: reference/operator/query/regex


Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

The page describes a prefix expression and separately explains a case-insensitive match but does not explain how the latter affects the former.

I think the prefix expression explanation should also state that using a case insensitive match will prevent a prefix expression from being optimized. A full index scan results in this case not one bounded by the prefix.

Separately it seems MongoDB could optimize the case-insensitive search for a prefix expression by simply restricting the search to two ranges: one starting with a lower-cased initial character and the other starting with an upper-cased initial character from the prefix. That would, on average be 26x faster than what happens today.



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:53:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.