[SERVER-1212] tighter index bounds for negated regular expression Created: 10/Jun/10  Updated: 15/Jun/15  Resolved: 15/Jun/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Aaron Staple Assignee: David Storch
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-667 implement tightest btree bounds possi... Closed
depends on SERVER-1211 don't use simplifiedQuery() to negate... Closed
is depended on by SERVER-1213 allow splitting new $or range in two Closed
Related
is related to SERVER-7261 field range with $not should properly... Closed
Participants:

 Description   

If we have {a:{$gt:"a",$lt:"r",$not:/^f/}} we'll still scan the strings beginning with f.



 Comments   
Comment by David Storch [ 15/Jun/15 ]

We currently do not have plans to change how we index negated regular expression predicates. Closing as "Won't Fix".

Comment by Aaron Staple [ 31/Aug/10 ]

I had intended for this bug to cover all sorts of negated ranges, including $ne and $not ranges. I also created SERVER-667 for all the $not negated ranges. This bug is scheduled for 1.7 early, while SERVER-667 for 1.7.x. Please let me know if the $not ranges should be 1.7 early or not.

I've done $ne and will be working on $nin next.

Comment by auto [ 30/Aug/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1212 deal with elemMatch later
http://github.com/mongodb/mongo/commit/efc06b3a6c456935a613c58dbcfe90ec7d9dfeed

Comment by auto [ 30/Aug/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-1212 ne range negation checkpoint
http://github.com/mongodb/mongo/commit/3b6de560b8862660f0da57b631de77731c316248

Generated at Thu Feb 08 02:56:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.