[SERVER-32629] $lookup misses results when both the mongos and primary shard are unaware that an involved collection is sharded Created: 10/Jan/18 Updated: 27/Oct/23 Resolved: 22/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Description |
|
Found while working on test cases for 1. Create unsharded local and foreign collections, inserting a few documents to each. |
| Comments |
| Comment by Kaloian Manassiev [ 22/Apr/20 ] |
|
This issue is now gone away as a result of the changes done under |
| Comment by Kaloian Manassiev [ 10/Jan/18 ] |
|
I think it should stay open so that the respective tests can be written, once the dependent bug is fixed. |
| Comment by Andy Schwerin [ 10/Jan/18 ] |
|
So, close as duplicate? |
| Comment by Kaloian Manassiev [ 10/Jan/18 ] |
|
This scenario is not limited to $lookup only. I believe any query will encounter the same problem. |
| Comment by Esha Maharishi (Inactive) [ 10/Jan/18 ] |
|
kaloian.manassiev, will this be solved once shards have an "unknown" metadata state? |