Skip to content
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

Rename UseKeywordScoring to mention BM25 #778

Merged
merged 2 commits into from
May 7, 2024
Merged

Rename UseKeywordScoring to mention BM25 #778

merged 2 commits into from
May 7, 2024

Conversation

jtibshirani
Copy link
Member

It's confusing to call this UseKeywordScoring, since we do not use it for the
keyword patterntype in Sourcegraph. This commit clarifies the name to mention
BM25.

@cla-bot cla-bot bot added the cla-signed label May 7, 2024
@jtibshirani jtibshirani requested a review from a team May 7, 2024 17:12
Copy link
Contributor

github-actions bot commented May 7, 2024

Fuzz test failed on commit 761bd1f. To troubleshoot locally, use the GitHub CLI to download the seed corpus with

gh run download 8989526155 -n testdata

api.go Show resolved Hide resolved
@jtibshirani jtibshirani merged commit 4e674a4 into main May 7, 2024
9 checks passed
@jtibshirani jtibshirani deleted the jtibs/bm25 branch May 7, 2024 17:57
// Currently, this treats each match in a file as a term and computes an approximation to BM25.
// When enabled, all other scoring signals are ignored, including document ranks.
bool use_keyword_scoring = 15;
bool use_bm25_scoring = 15;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ggilmore is it safe to rename this field in the proto file? Don't know enough about grpc :) I'm assuming yes since the type didn't change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants