Skip to content

Commit 2e2931f

Browse files
committed
*
1 parent 7995f81 commit 2e2931f

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

source/mapping-rules/mapping-rule-options/time-series.txt

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,9 @@ About this Task
2222
- You can use :ref:`field customizations <rm-field-customizations>` to
2323
convert string columns to datetime fields in Relational Migrator.
2424

25-
- CDC jobs that have time series configurations do not create the
26-
time series collections until the CDC job completes.
25+
- :abbr:`CDC (Change Data Capture)` jobs that have time series
26+
configurations do not create the time series collections until the
27+
CDC job completes.
2728

2829
- Compared to normal collections, storing time series data in time series
2930
collections improves query efficiency and reduces the disk usage for
@@ -43,10 +44,10 @@ Before you Begin
4344
series data as a separate sync job. This can make it easier to
4445
preload a large time series collection and migrate the rest of your data after the initial job completes.
4546

46-
- If your migrating larges amounts of data, consider using
47-
:ref:`table filters <rm-table-filters>` to batch your sync jobs
48-
based on logical conditions. For example, you might import one year
49-
of historical data at a time using table filters. This allows you to break down a large
47+
- If you're migrating large amounts of data, you might want to utilize
48+
:ref:`table filters <rm-table-filters>` to divide your sync jobs into
49+
batches. For example, you might import one year of historical data at
50+
a time using table filters. This allows you to break down a large
5051
job into more manageable segments.
5152

5253
- If a long-running sync job fails unexpectedly (for example, due to a
@@ -87,16 +88,16 @@ Steps
8788
If you have multiple datetime columns must select a
8889
single field per timeseries collection.
8990

90-
#. (Optional) Select a :guilabel:`Meta Field`.
91+
#. (Optional) Select a :guilabel:`Meta Field`
9192

9293
``Meta Field`` is the name of the field that contains metadata
9394
in each time series document. The metadata in the specified
9495
field is used to label a unique series of
95-
documents. The metadata should rarely, if ever, change.
96+
documents. The metadata should rarely change.
9697

9798
#. Select a :guilabel:`Granularity`.
9899

99-
``Granularity`` should be a value that most closely matches
100+
Specify a ``Granularity`` value that most closely matches
100101
the time between consecutive incoming timestamps. Setting the correct granularity
101102
improves performance by optimizing how MongoDB stores data in the
102103
collection. Possible values are ``seconds``, ``minutes``, and
@@ -115,8 +116,7 @@ Steps
115116

116117
When a collection is configured with a time series field,
117118
the time series icon :icon-lg:`TimeSeries` displays next to the collection
118-
name on the :guilabel:`Schema model` pane. This icon
119-
indicates the collection is a time series collection.
119+
name on the :guilabel:`Schema model` pane.
120120

121121
Example
122122
-------

0 commit comments

Comments
 (0)