feat: added span_count using the MV and index v3 traces table [Design needs to be finalised] #6674
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.
Summary
Related Issues / PR's
Screenshots
NA
Affected Areas and Manually Tested Areas
Important
Added support for sorting trace queries by span count using a new
sortBy
parameter in query functions.sortBy
parameter toprepareTracesQueryFunc
inquery_builder.go
to support sorting by span count.PrepareTracesQuery
inquery_builder.go
,v3/query_builder.go
, andv4/query_builder.go
to handlesortBy
parameter.TraceSortBySpanCount
andTraceSortByTraceDuration
constants inconstants.go
.buildTracesQuery
inv3/query_builder.go
andv4/query_builder.go
to include logic for sorting by span count usingTraceExplorerSpanCountSubQuery
.SIGNOZ_TRACE_SPAN_COUNT_MV
for span count sorting.SortBy
field toQueryRangeParamsV3
inv3.go
.This description was created by for cdeb0af. It will automatically update as commits are pushed.