[SERVER-4778] inconsistent sizing for "$in combinatorial limit of result set" messages Created: 25/Jan/12 Updated: 28/Jan/15 Resolved: 28/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | David Storch |
| Resolution: | Incomplete | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
With FieldRangeVector() the limit is 1000000, with FieldRangeSet::indexBounds() the limit is 4000000. The FieldRangeVector() should be a lot more scalable than FieldRangeSet::indexBounds(), so we might consider use of an even higher limit for that case. Currently FieldRangeVector() is used for btree traversal and FieldRangeSet::indexBounds() is used when figuring out which shards an operation should go to. |
| Comments |
| Comment by David Storch [ 28/Jan/15 ] |
|
This ticket refers to old code that has been removed from the codebase. Closing as Incomplete. |
| Comment by auto [ 07/Feb/12 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |