From 39068f00b0f2f4a0968e6d009f3381215acfc2a3 Mon Sep 17 00:00:00 2001 From: Asya Kamsky Date: Mon, 14 Jul 2014 12:17:26 -0700 Subject: [PATCH] as of 2.6 that note shouldn't be there Removing thing referencing 16MB limit for agg. --- source/core/aggregation-introduction.txt | 3 --- 1 file changed, 3 deletions(-) diff --git a/source/core/aggregation-introduction.txt b/source/core/aggregation-introduction.txt index 0d428f1de80..5468cfe0416 100644 --- a/source/core/aggregation-introduction.txt +++ b/source/core/aggregation-introduction.txt @@ -64,9 +64,6 @@ the custom JavaScript provide great flexibility compared to the aggregation pipeline, in general, map-reduce is less efficient and more complex than the aggregation pipeline. -Additionally, map-reduce operations can have output sets that -exceed the 16 megabyte output limitation of the aggregation pipeline. - .. note:: Starting in MongoDB 2.4, certain :program:`mongo` shell functions and properties are inaccessible in map-reduce operations. MongoDB 2.4 also provides support for multiple