-
Notifications
You must be signed in to change notification settings - Fork 606
Proposal: query span id with no leading zeros #5343
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
base: main
Are you sure you want to change the base?
Proposal: query span id with no leading zeros #5343
Conversation
pkg/traceql/ast_conditions.go
Outdated
operand := o.RHS.(Static) | ||
if o.LHS.(Attribute).Intrinsic == IntrinsicSpanID { | ||
operand = normalizeSpanIDOperand(operand) | ||
o.RHS = operand // Update the operation with the normalized operand |
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'm not sure whether it's the right way to do to change LHS/RHS inside extractConditions
0b7fe7d
to
ea4ecae
Compare
ea4ecae
to
6a71b19
Compare
6a71b19
to
b8e4031
Compare
{ | ||
Op: "Equal", | ||
CompareCond: `bytes.Equal(bytes.TrimLeft(vv, "\x00"), p.value)`, | ||
RangeCond: "", |
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 don't really like that we have to skip RangeCond
. Maybe it would be better to add/remove leading zeroes on write as we do for trace id?
What this PR does:
Fixes search by span id without leading zeros
Contains #5331. Diff is in the last 3 commits
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]