[SERVER-32282] Aggregation text search returns text score even if it wasn't requested when targeting multiple shards in a sharded cluster Created: 12/Dec/17 Updated: 30/Oct/23 Resolved: 16/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | 3.6.0 |
| Fix Version/s: | 3.6.2, 3.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | |||||||||||||||||||||||||||||
| Operating System: | ALL | |||||||||||||||||||||||||||||
| Backport Requested: |
v3.6
|
|||||||||||||||||||||||||||||
| Steps To Reproduce: | I think the easiest way is to try running existing tests: first, apply this patch to run with multiple shards:
and then run
With this patch applied, I can't reproduce the failure locally:
|
|||||||||||||||||||||||||||||
| Sprint: | Query 2017-12-18, Query 2018-01-01 | |||||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||||
| Description |
|
As part of
will return the text score even though it hasn't been requested. This seems like a bug, as it differs from the behavior of the find command, which does not return the text score. Interestingly, this only occurs when the query targets multiple shards in the cluster. If I add a predicate on the shard key and target one shard, the text score is not included. charlie.swanson noted that this might be related to the change in |
| Comments |
| Comment by Githook User [ 29/Dec/17 ] |
|
Author: {'username': 'gormanb', 'email': 'bernard.gorman@gmail.com', 'name': 'Bernard Gorman'}Message: (cherry picked from commit 6cbca62471218a08a4fdf8785bd1e1e38cf9bde3) |
| Comment by Githook User [ 16/Dec/17 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: |
| Comment by Bernard Gorman [ 13/Dec/17 ] |
|
Thanks kyle.suarez, looking at this now. The reason this doesn't manifest for the single-shard case is that, when we can target the query to a single shard, we now pass the entire pipeline through to that shard and no split/merge semantics take place. |