Put ingester disable chunk trimming a feature flag #6300
Merged
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.
Signed-off-by: Ben Ye [email protected]<!-- Thanks for sending a pull request! Before submitting:
-->
What this PR does:
This changes #6270 to mark the behavior optional under a feature flag.
We noticed that query result got changed if disabling chunk trimming for the following test case, captured by fuzz test.
https://github.com/cortexproject/cortex/actions/runs/11621920479/job/32367371250?pr=6298
The failure seems correctly captured as
timestampfunction returns timestamp of the sample so if certain samples are not trimmed then the result changes.I think the behavior is not intended but let's make disable chunk trimming a feature flag for now and users can enable it at their own risk
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]