[DOCS-13323] Investigate changes in SERVER-40687: Positional projection ($) only considers first path component when comparing to query document Created: 02/Jan/20 Updated: 13/Nov/23 Resolved: 25/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3, 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: | Fixed | Votes: | 0 |
| Labels: | docs-query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 32 weeks, 6 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
| Comments |
| Comment by Githook User [ 25/Jun/20 ] | ||||||
|
Author: {'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: ( | ||||||
| Comment by Jeffrey Allen [ 10/Jun/20 ] | ||||||
|
Thanks ian.boros! This clears things up. | ||||||
| Comment by Ian Boros [ 10/Jun/20 ] | ||||||
|
Hi jeffrey.allen, You have the right idea. In general this new behavior is only really useful for cases where you have "parallel arrays". The following now works in 4.4, but did not in 4.2.
In 4.2, you could do this when the field we're filtering on and the field we're projecting had a common parent. For example:
So, 4.4 expanded this to work on top-level fields as well. In general this is only useful when the the field with positional projection is an array and the field with the filter is an array. |