Add support for vector and scalar types in gRPC query range #6225
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
The gRPC query range method does not send back results when the result type is a vector or scalar. An example of a range query that returns a vector is absent(metric). This commit adds support for those two response types. Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
36d6e48 to
813240c
Compare
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.
The gRPC query range method does not send back results when the result type is a vector or scalar. An example of a range query that returns a vector is absent(metric). A range query with the same start and end time also seems to return a vector instead of a matrix.
This commit adds support for those two response types.
Changes
Verification
Manual testing locally.