Skip to content

Commit 2c6836f

Browse files
kay-kimSam Kleinman
authored andcommitted
DOCS-1254 powerOf2 textindex and DOCS-1247 geoWithin in agg
Signed-off-by: Sam Kleinman <[email protected]>
1 parent 8784278 commit 2c6836f

File tree

4 files changed

+22
-12
lines changed

4 files changed

+22
-12
lines changed

source/core/indexes.txt

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -796,6 +796,9 @@ the supported languages.
796796
``text`` indexes have the following storage requirements and
797797
performance costs:
798798

799+
- Text indexes change the space allocation method for the documents in
800+
the collection to :collflag:`usePowerOf2Sizes`.
801+
799802
- Text indexes can be large. They contain one index entry for each
800803
unique post-stemmed word in each indexed field for each document
801804
inserted.

source/reference/aggregation/match.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ $match (aggregation)
8787

8888
.. versionadded:: 2.4
8989
:pipeline:`$match` queries can support the
90-
geospatial :mongodb:operator:`$within` operations.
90+
geospatial :mongodb:operator:`$geoWithin` operations.
9191

9292
.. warning::
9393

source/reference/operator/geoWithin.txt

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ $geoWithin
1111
The :operator:`$geoWithin` operator is a geospatial query operator
1212
that queries for a defined point, line or shape that exists entirely
1313
within another defined shape. When determining inclusion, MongoDB
14-
considers the border of a shape to be part of the shape (subject to
15-
the precision of floating point numbers).
14+
considers the border of a shape to be part of the shape, subject to
15+
the precision of floating point numbers.
1616

1717
The :operator:`$geoWithin` operator queries for inclusion in a
1818
:term:`GeoJSON` polygon or a shape defined by legacy coordinate
@@ -26,6 +26,11 @@ $geoWithin
2626
The ``2dsphere`` and ``2d`` indexes both support the
2727
:operator:`$geoWithin` operator.
2828

29+
.. versionchanged:: 2.2.3
30+
:operator:`$geoWithin` no longer requires a geospatial
31+
index. However, a geospatial index will improve query
32+
performance.
33+
2934
If querying for inclusion in a GeoJSON polygon on a sphere, pass the
3035
polygon to :operator:`$geoWithin` through the :operator:`$geometry`
3136
operator. Coordinates of a polygon are an array of LinearRing
@@ -80,7 +85,7 @@ $geoWithin
8085
{ <shape operator> : <coordinates>
8186
} } } )
8287

83-
For the syntax for a shape operator, see:
88+
For the syntax of a shape operator, see:
8489

8590
- :operator:`$box`
8691

@@ -93,5 +98,4 @@ $geoWithin
9398
.. operator:: $within
9499

95100
.. deprecated:: 2.4
96-
In 2.4, :operator:`$geoWithin` replaces :operator:`$within`.
97-
101+
:operator:`$geoWithin` replaces :operator:`$within` in MongoDB 2.4.

source/release-notes/2.4.txt

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Release Notes for MongoDB 2.4 (2.3 Development Series)
66

77
MongoDB 2.4 is currently in development, as part of the 2.3
88
development release series. While 2.3-series releases are currently
9-
available, these versions of MongoDB, including the 2.4 release
9+
available, these versions of MongoDB, including the 2.4 release
1010
candidate builds, are for *testing only and
1111
not for production use*.
1212

@@ -91,7 +91,10 @@ query operator for queries on GeoJSON data:
9191

9292
The operators use the new :operator:`$geometry` parameter.
9393

94-
For more information, see:
94+
Additionally, :operator:`$geoWithin` instead no longer requires a
95+
geospatial index.
96+
97+
For more information on geospatial indexes in 2.4, see:
9598

9699
- :doc:`/applications/geospatial-indexes`
97100

@@ -466,9 +469,12 @@ MongoDB 2.4 introduces a number of additional functionality and
466469
improved performance for the :doc:`Aggregation Framework
467470
</applications/aggregation>`. Consider the following additions in 2.4:
468471

469-
- :agg:pipeline:`$match` queries now support the :operator:`$within`
472+
- :agg:pipeline:`$match` queries now support the :operator:`$geoWithin`
470473
operator for bounded geospatial queries.
471474

475+
- The new :agg:pipeline:`$geoNear` pipeline stage to support
476+
geospatial queries.
477+
472478
- :agg:group:`$min` operator only considers non-null and existing field
473479
values. If all the values for a field are ``null`` or are missing,
474480
the operator returns ``null`` for the minimum value.
@@ -482,6 +488,3 @@ improved performance for the :doc:`Aggregation Framework
482488
portion of a date.
483489

484490
- The new :agg:expression:`$concat` operator concatenates array of strings.
485-
486-
- The new :agg:pipeline:`$geoNear` pipeline stage to supports
487-
geospatial queries.

0 commit comments

Comments
 (0)