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

Add field-specific rank filter-threshold setting #33165

Merged

Conversation

vekterli
Copy link
Member

@geirst please review
@toregge FYI

With this commit rank-profile supports two rank variants, where the latter is newly introduced:

rank-profile my_profile {
  rank foo_field: filter

  rank bar_field {
    filter-threshold: 0.03
  }
}

With this commit, `rank-profile` supports two `rank` variants,
where the latter is newly introduced:

```
rank-profile my_profile {
  rank foo_field: filter

  rank bar_field {
    filter-threshold: 0.03
  }
}
```
@vekterli vekterli requested a review from geirst January 23, 2025 14:31
geirst added a commit that referenced this pull request Jan 23, 2025
This threshold is currently used to determine whether to use bitvector posting list when searching in a disk index.
This optimization is triggered when the relative hit estimate of the query term is larger than the filter threshold.

This relates to #33139 and #33165 (schema syntax) and #33156 (config wiring).
@vekterli vekterli merged commit f402ed5 into master Jan 24, 2025
3 checks passed
@vekterli vekterli deleted the vekterli/add-field-specific-rank-filter-threshold-setting branch January 24, 2025 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants