[SERVER-3973] Add support for sorting and limiting inline map/reduce Created: 29/Sep/11  Updated: 06/Dec/22  Resolved: 04/Feb/22

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

Type: Improvement Priority: Major - P3
Reporter: Oliver Assignee: Backlog - Query Optimization
Resolution: Done Votes: 17
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query Optimization
Participants:

 Description   

I don't need permanent outputs, so I switched to inline. Now the whole
map/reduce result is returned. Before I had the chance to query the
tmp collection with find(),sort() and limit(). Is there any way to
sort and limit the output of an inline map/reduce?

In my case I have like 10,000 items at my inline output, and I don't
want to crop it with my client language to 10 results.

Might be an improvement to offer something to do this.



 Comments   
Comment by Esha Bhargava [ 04/Feb/22 ]

Closing these tickets as part of the deprecation of mapReduce.

Comment by Frederico Ramos [ 19/Jul/17 ]

+1 for this feature. Would be extremely useful for web apps

Comment by Guillaume Sabran [ 20/Sep/16 ]

any update? This would indeed be extremely helpful for a web server that runs such query on a user basis

Comment by Simone Busoli [ 28/Jul/14 ]

Is this still not supported? Strange that the docs don't seem to mention it, and at least I would expect some sort of error when trying to use sort and/or limit with an inline output.

Comment by vijaya baskar [ 30/Jul/13 ]

I can understand that map reduce is for background tasks, but having this feature could increase its usability in online/interactive applications.

Comment by George L [ 24/Jul/13 ]

This would be very helpful in web apps scenarios, where perhaps output of mapreduce is unique to each user.

Comment by Jon Ursenbach [ 18/Aug/12 ]

Having this ability would be very much appreciated.

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