feat: support attributes and limit in APIv3 HTTP Gateway (fixes #7594) #7968
Conversation
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
kyyril
force-pushed
the
fix/apiv3-http-find-traces-params
branch
2 times, most recently
from
0364c94 to
b89cdc7
Compare
…rtracing#7594) Signed-off-by: kyyril <khairilrahman55@gmail.com>
kyyril
force-pushed
the
fix/apiv3-http-find-traces-params
branch
from
535065f to
1892c4b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Enhances the APIv3 HTTP gateway to support attributes (via query.tag) and search limit (via query.limit or query.num_traces) parameters. This brings the HTTP gateway to parity with the gRPC findTraces implementation and addresses #7594.