Skip to content

Commit 9e2f2e3

Browse files
authored
Active voice edit.
1 parent fb91644 commit 9e2f2e3

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

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

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -126,9 +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-
On a clustered environment, if `COMPACTION_POLICY` is set, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) for all time series key names.
130-
This will force each compaction to be created in the same hash slot as its source key.
131-
Failure to do so can result in data not being compacted with no 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 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.
132130
{{% /warning %}}
133131

134132
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)