[SERVER-32538] lookup.js should not drop the local collection after sharding it Created: 03/Jan/18  Updated: 27/Oct/23  Resolved: 21/Dec/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Bug 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

Assigned Teams:
Query
Operating System: ALL
Participants:

 Description   

The test runs through a suite of tests with all collections unsharded, then shards the local collection, and runs through the same suite of tests. Since the collection is dropped in a few places (like here), this may not be testing what is intended.

Note this may go away/change as part of the sharded $lookup project.



 Comments   
Comment by Charlie Swanson [ 21/Dec/18 ]

james.wahlin I believe this went away as part of SERVER-32308.

Generated at Thu Feb 08 04:30:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.