Skip to content

fix(summaries): Use Op.EQ instead of Op.IN for a scalar value filter in Snuba query#110693

Merged
shashjar merged 10 commits intomasterfrom
shashjar/fix-summaries-snuba-query-condition-eq-instead-of-in
Mar 16, 2026
Merged

fix(summaries): Use Op.EQ instead of Op.IN for a scalar value filter in Snuba query#110693
shashjar merged 10 commits intomasterfrom
shashjar/fix-summaries-snuba-query-condition-eq-instead-of-in

Conversation

@shashjar
Copy link
Member

We should be using Op.EQ here for a scalar value filter on this Snuba query, instead of Op.IN.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Mar 13, 2026
Base automatically changed from shashjar/implement-summaries-task-errors-query-occurrences-on-eap to master March 16, 2026 18:49
@shashjar shashjar requested a review from a team March 16, 2026 18:51
@shashjar shashjar marked this pull request as ready for review March 16, 2026 18:51
@shashjar shashjar merged commit 3a518c5 into master Mar 16, 2026
57 checks passed
@shashjar shashjar deleted the shashjar/fix-summaries-snuba-query-condition-eq-instead-of-in branch March 16, 2026 20:25
JonasBa pushed a commit that referenced this pull request Mar 16, 2026
…ter in Snuba query (#110693)

We should be using `Op.EQ` here for a scalar value filter on this Snuba
query, instead of `Op.IN`.

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants