[DOCS-13210] Investigate changes in SERVER-44056: regression in {$meta: "textScore"} projection Created: 07/Nov/19 Updated: 13/Nov/23 Resolved: 21/Feb/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Jeffrey Allen |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | docs-grab-bag | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 50 weeks, 5 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary In 4.2, a find() command with a textScore $meta projection, e.g. would assign a value of 0 to 'a' if no textScore metadata was available. The default value in 4.3/master is missing (that is, 'a' will not be present in the returned document). Feel free to slack me if you have questions. Description of Linked TicketA Java driver functional test of {$meta: "textScore"} projection recently regressed when running against latest mongod. The regression occurred somewhere between the commit hashes 560b542 and c119ef4. Test setup:
Expected results contain a synthetic score field:
Results after the regression omit the score field:
Educated guess is that the fix for Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Jeffrey Allen [ 21/Feb/20 ] | ||||||||
|
Behavior changed in | ||||||||
| Comment by Jeffrey Allen [ 21/Feb/20 ] | ||||||||
|
Thanks david.storch, I'll close this one. | ||||||||
| Comment by David Storch [ 21/Feb/20 ] | ||||||||
|
jeffrey.allen, ah, yeah that sounds right. You're correct that the behavior introduced for this example in
Therefore, it probably makes sense to close this ticket as superseded by |