Remove Experimental property feature flag#6416
Merged
ddanielr merged 2 commits intoJun 10, 2026
Merged
Conversation
Removes the `gc.remove.in.use.candidates` feature flag property that was restricting the gc behavior from removing gc candidates for files that were still referenced by other tablets.
Contributor
Author
|
See #3693 for additional context |
dlmarion
approved these changes
Jun 8, 2026
Replaced the hardcoded path values with method calls for tests that used the exact same path for file reference creation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Removes the
gc.remove.in.use.candidatesfeature flag property that was restricting the gc behavior from removing gc candidates for files that were still referenced by other tablets.Closes: #6412
This feature was originally created for the 2.1.3 release line and should be elevated to standard GC behavior in 2.1.5.