feat(cleanup): Implement pauseless table segment cleanup logic #15002
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.
Behavior Details
The endpoint resets segment state for pauseless-enabled tables in two modes:
Mode 1: Explicit Error Segments
When error segments are provided via the
segments
query parameter:Mode 2: Automatic Detection
When no error segments are provided, for each partition:
Retention Period Handling
The retention period for deleted segments follows this precedence:
retention
query param)Note: Use 0d or -1d for immediate deletion without retention
API: DELETE /resetPauselessTable/{tableName}
Flags: ?type=[OFFLINE|REALTIME]&retention=[period]&segments=[list]