SERVER-35043, SERVER-22949: move geoNear implementation into aggregation

This commit removes the geoNear command and moves its implementation
into the aggregation framework. Users should use the aggregate command
with a $geoNear stage.

The implementation rewrite additionally removes the limit in the
$geoNear aggregation stage. To limit the number of results, use a $limit
stage.

1 files changed, 7 insertions, 4 deletions

diff --git a/jstests/core/geod.js b/jstests/core/geod.js
index 35844d0f914..055453254a5 100644
--- a/jstests/core/geod.js
+++ b/jstests/core/geod.js
@@ -7,8 +7,11 @@ t.ensureIndex({loc: "2d"});
 // should match no points in the dataset.
 dists = [.49, .51, 1.0];
 for (idx in dists) {
-    b = db.runCommand({geoNear: "geod", near: [1, 0], num: 2, maxDistance: dists[idx]});
-    assert.eq(b.errmsg, undefined, "A" + idx);
-    l = b.results.length;
-    assert.eq(l, idx, "B" + idx);
+    b = db.geod
+            .aggregate([
+                {$geoNear: {near: [1, 0], distanceField: "d", maxDistance: dists[idx]}},
+                {$limit: 2},
+            ])
+            .toArray();
+    assert.eq(b.length, idx, "B" + idx);
 }