[SERVER-8593] Incorrect results when projecting a field with a hashed index Created: 15/Feb/13 Updated: 06/Dec/22 Resolved: 07/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.2.3, 2.4.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sridhar Nanjundeswaran | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
2.2.3 and 2.4.0-rc0 on OS X |
||
| Assigned Teams: |
Query
|
|||||||||
| Operating System: | ALL | |||||||||
| Steps To Reproduce: |
|
|||||||||
| Participants: |
| Description |
|
From the documentation you cannot use hashed indexes for range queries. Hence expect the query below to either error out or return the correct result. |
| Comments |
| Comment by David Storch [ 07/Jan/16 ] | ||||||||
|
It looks like this has been fixed, probably as part of the query engine rewrite first released in version 2.6.0:
Closing as Gone Away. | ||||||||
| Comment by Scott Hernandez (Inactive) [ 03/Mar/13 ] | ||||||||
|
The range query doesn't make a lot of sense for a hashed index, but this does to get values from the index instead of docs:
This returns the hash value, not the field value.
| ||||||||
| Comment by Sridhar Nanjundeswaran [ 15/Feb/13 ] | ||||||||
|
One more minor test. If the query is changed to an equality it does the right thing too.
|