Skip to content

Align the warning with COMPACTION_POLICY warning #1201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 24, 2025
Merged

Align the warning with COMPACTION_POLICY warning #1201

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2512844
Align the warning with COMPACTION_POLICY warning
LiorKogan Feb 23, 2025
3a34606
Apply suggestions from code review
dwdougherty Feb 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/commands/ts.createrule/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ aggregates results into time buckets.
- Deleting `destKey` will cause the compaction rule to be deleted as well.

{{% warning %}}
On a clustered environment, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) to force `sourceKey` and `destKey` to be stored in the same hash slot.
On a clustered environment, you must use [hash tags]({{< relref "/operate/oss_and_stack/reference/cluster-spec" >}}#hash-tags) to force `sourceKey` and `destKey` to be stored in the same hash slot. If you don't, Redis may fail to compact the data without displaying any error messages.
{{% /warning %}}

</note>
Expand Down