[SERVER-59467] Deprecation of map/reduce is pretty uninspired Created: 20/Aug/21  Updated: 06/Dec/22  Resolved: 03/Sep/21

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

Type: Bug Priority: Major - P3
Reporter: Valentin Popescu Assignee: Backlog - Triage Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Triage
Participants:

 Description   

Problem Statement/Rationale

Sharded collections can not be used in aggregation pipelines lookups nor can they be sent into the aggregation pipelines from exterior similar to scope, or at least we don't know how to do that... 

Steps to Reproduce

Tried and failed to migrate an existing incremental map / reduce job to aggregation pipeline. The job has a lot of scoped variables and prior lookups that it has to do and they are lookups in heavily sharded collections.

Expected Results

If aggregation pipeline is pushed as the only alternative people should use then it would be good if it is possible to do the same things with it.

Actual Results

Doesn't work



 Comments   
Comment by Edwin Zhou [ 03/Sep/21 ]

Hi valentin@zalter.com,

Thanks for your report. Please note that the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Developer Community Forums. If your discussion there leads you to believe that a specific improvement can be made, please let us know and we will be happy to investigate!

Best,
Edwin

Comment by Ryan Chipman [ 20/Aug/21 ]

Hi valentin@zalter.com, the TOOLS project is for the MongoDB Database Tools (mongodump, mongorestore, mongoimport, mongoexport, mongotop, mongostat, and bsondump). I've moved this ticket to the SERVER project, since your issue is with functionality in MongoDB Server

Generated at Thu Feb 08 05:47:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.