Skip to content

Commit 88294a7

Browse files
authored
Apply review comments.
1 parent 9e2f2e3 commit 88294a7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/develop/data-types/timeseries/configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ Each rule is separated by a semicolon (`;`), the rule consists of multiple field
126126
Assure that there is a bucket that starts at exactly _alignTimestamp_ after the epoch and align all other buckets accordingly. Default value: 0 (aligned with the epoch). Example: if _bucketDuration_ is 24 hours, setting _alignTimestamp_ to `6h` (6 hours after the Epoch) will ensure that each bucket’s timeframe is [06:00 .. 06:00).
127127

128128
{{% warning %}}
129-
In a clustered environment, if you set `COMPACTION_POLICY`, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names. This ensures that the system creates each compaction in the same hash slot as its source key. If you don't, the system may fail to compact the data without displaying any error messages.
129+
In a clustered environment, if you set `COMPACTION_POLICY`, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names. This ensures that Redis will create each compaction in the same hash slot as its source key. If you don't, the system may fail to compact the data without displaying any error messages.
130130
{{% /warning %}}
131131

132132
When a compaction policy is defined, compaction rules will be created automatically for newly created time series, and their key would be set to:

0 commit comments

Comments
 (0)