[SERVER-36990] Indexed filed still exists in FETCH step Created: 05/Sep/18 Updated: 05/Sep/18 Resolved: 05/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 3.4.4 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Meng | Assignee: | Nick Brewer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
I have a compound index:
When I do a query:
which hit the index field1_1_field2_1_field3_1, and in executionStats' IXSCAN step, field3's range is [null, null]. BUT, { field3: { $eq: null }} exists in FETCH step ??? I have indexed it and use it in IXSCAN step, why mongo need to filter it again ? |
| Comments |
| Comment by Nick Brewer [ 05/Sep/18 ] |
|
ByLomo This is expected behavior; see Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. -Nick |