You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem - what in Jaeger blocks you from solving the requirement?
The array of searchRequests is been maked Outside the for loop,the length of it equals the slice of traceIds. When it query second time in the for loop,the length of traceIds will be changed,but the length of searchRequests will not. This bug may cause repeated traceId be queried.like this:
There is #duplicated span in this trace
Proposal - what do you suggest to solve the problem or improve the existing situation?
Maybe we can initial searchRequests in for loop,the length of it will equals the slice of traceIds Always.
Any open questions to address
The text was updated successfully, but these errors were encountered:
Requirement - what kind of business use case are you trying to solve?
When using the search function of jaeger-query, if the data to be queried is very large, the method multiRead in "github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/reader.go" will query the storage more than once. There is a bug in this method that causes queried data may be repeated probably.
https://github.com/jaegertracing/jaeger/blob/master/plugin/storage/es/spanstore/reader.go
Problem - what in Jaeger blocks you from solving the requirement?
The array of searchRequests is been maked Outside the for loop,the length of it equals the slice of traceIds. When it query second time in the for loop,the length of traceIds will be changed,but the length of searchRequests will not. This bug may cause repeated traceId be queried.like this:
There is #duplicated span in this trace
Proposal - what do you suggest to solve the problem or improve the existing situation?
Maybe we can initial searchRequests in for loop,the length of it will equals the slice of traceIds Always.
Any open questions to address
The text was updated successfully, but these errors were encountered: