Add protobuf internal query result payload format to experimental features list. #4429
Conversation
This file contains 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
3 tasks
charleskorn
force-pushed
the
charleskorn/add-experimental-feature
branch
from
c1276a4
to
354e5e6
Compare
pracucci
approved these changes
Mar 9, 2023
osg-grafana
pushed a commit
that referenced
this pull request
Mar 9, 2023
charleskorn
added a commit
that referenced
this pull request
Mar 10, 2023
…tures list. Cherry pick part of #4429 that is included in v2.7.
Merged
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does
This PR adds the new internal query result payload format to the experimental features list.
As part of this feature (covering the querier -> query-frontend path) is included in v2.7, once this is merged I'll also backport the relevant part to the 2.7 release as well.
Which issue(s) this PR fixes or relates to
#4104
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]