DOC-1720 Customer-Incident-Delete Records #1388
Draft
+16
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request improves documentation related to deleting records from a topic in Redpanda. The main focus is on clarifying the risks of using timestamps with the
rpk topic trim-prefix
command and ensuring users are aware of potential unintended data loss.warning-delete-records.adoc
) that explains the risks of using timestamps withrpk topic trim-prefix
, including potential for truncating an entire partition if timestamps are unordered.delete-topic-records.adoc
) and therpk topic trim-prefix
reference documentation to alert users in both contexts. [1] [2]Resolves https://redpandadata.atlassian.net/browse/DOC-1720
Review deadline:
Page previews
rpk topic trim prefix (SM, Cloud)
Delete records from a topic (SM, Cloud)
Checks