feat(issue-search): per-request weight override for recommended_v2 sort#118365
Draft
roggenkemper wants to merge 1 commit into
Draft
feat(issue-search): per-request weight override for recommended_v2 sort#118365roggenkemper wants to merge 1 commit into
roggenkemper wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
Scope: Backend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7e003a5. Configure here.
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
roggenkemper
force-pushed
the
roggenkemper/recommended-v2-staff-weight-override
branch
2 times, most recently
from
b046862 to
0cee70b
Compare
roggenkemper
changed the title
Compare alternate recommended_v2 weights against the live default in a single
request via ?recommendedWeights={...}, without touching options or adding a
second sort. The weights override the registered options for that request only
and rerank just the requester's own feed: base factors flow into the Snuba
aggregation through the existing aggregate_kwargs channel, boost weights rebuild
the score_fn, and any unspecified weight falls back to options.
Gated to the recommended_v2 sort since aggregate_kwargs is shared with trends.
Payload is sanitized before it reaches the ClickHouse scoring SQL: weights and
boost values must be finite floats, and group-type-boost keys are coerced to ints.
Co-Authored-By: Claude <noreply@anthropic.com>
roggenkemper
force-pushed
the
roggenkemper/recommended-v2-staff-weight-override
branch
from
2ab3f51 to
0794a5f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Allow passing in alternate
recommended_v2weights against the live default side by side.How it works
GET ...?sort=recommended_v2&recommendedWeights={"event_volume":0.05,"spike":0,"severity":0.3,"assignment":0.3}The weights override the registered options for that request only:
recency/spike/severity/event-volume/user_impact/message_penalty/group_type_boost) flow into the Snuba aggregation via the existingaggregate_kwargschannel (recommended_aggregationalready received it; it just ignored it).assignment/fixability/agent/regressed/newness) rebuild therecommended_v2score_fnfor the request.