-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[remote-storage][v2] Add complete IDL for trace storage #6737
[remote-storage][v2] Add complete IDL for trace storage #6737
Conversation
Signed-off-by: Mahad Zaryab <[email protected]>
// The chunking rules are the same as for GetTraces. | ||
// | ||
// If no matching traces are found, an empty stream is returned. | ||
// If an error is encountered, the iterator returns the error and stops. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yurishkuro How should we handle error cases?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6737 +/- ##
=======================================
Coverage 96.04% 96.04%
=======================================
Files 364 364
Lines 20692 20692
=======================================
Hits 19874 19874
Misses 624 624
Partials 194 194
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
// There's currently an implementation-dependent ambiguity whether all query filters | ||
// (such as multiple tags) must apply to the same span within a trace, or can be satisfied | ||
// by different spans. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the api_v3 it's actually stated unambiguously
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
|
||
// FindTraceIDsResponse represents the response for FindTracesRequest. | ||
message FindTraceIDsResponse { | ||
repeated bytes trace_ids = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realized - shouldn't we be returning IDs with timestamps? We can do in a follow up PR, as it needs a change in storage API.
Signed-off-by: Mahad Zaryab <[email protected]>
Which problem is this PR solving?
Description of the changes
trace_storage.proto
by adding the remainingFindTraces
andFindTraceIDs
RPCs for theTraceReader
service, along with theExport
rpc for theTraceWriter
service.How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:npm run lint
andnpm run test