File tree Expand file tree Collapse file tree 1 file changed +8
-7
lines changed Expand file tree Collapse file tree 1 file changed +8
-7
lines changed Original file line number Diff line number Diff line change @@ -105,19 +105,20 @@ store data in time-order. This format provides the following benefits:
105105Behavior
106106~~~~~~~~
107107
108- Time series collections behave like normal collections. You can insert
109- and query your data as you normally would .
108+ Time series collections behave like typical collections. You insert
109+ and query data as usual .
110110
111111MongoDB treats time series collections as writable non-materialized
112112:ref:`views <views-landing-page>` backed by an internal collection. When
113113you insert data, the internal collection automatically organizes time
114114series data into an optimized storage format.
115115
116- Since MongoDB 6.3, when you create a new time series collection, MongodDB
117- generates a :ref:`compound index <index-create-compound>` on the
118- :ref:`metaField and timeField <time-series-fields>` fields. Queries on time
119- series collections take advantage of this index, as well as the optimized
120- storage format, to improve query performance.
116+ Starting in MongoDB 6.3: if you create a new time series collection,
117+ MongoDB also generates a :ref:`compound index <index-create-compound>`
118+ on the :ref:`metaField and timeField <time-series-fields>` fields. To
119+ improve query performance, queries on time series collections use the
120+ new compound index. The compound index also uses the optimized storage
121+ format.
121122
122123.. tip::
123124
You can’t perform that action at this time.
0 commit comments