You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strategy for computing the Attribute ranking criterion.
527
-
This mainly affects multi-word queries where matches occur in and across multiple attributes.
528
-
- `minProximity`.
529
-
Determine the best matching attribute from those with the best proximity score.
530
-
This is the default when Attribute follows Proximity in the `ranking` setting.
531
-
Ties on an ordered attribute are broken by the match position.
532
-
- `best`.
533
-
Determine the best matching attribute from all attributes matching any query term.
534
-
This is the default when Attribute comes before Proximity in the `ranking` setting.
535
-
Ties on an ordered attribute are broken by the match position.
536
-
- `sum`.
537
-
Instead of a single best attribute, compute a score across each query term's best matching attribute (and position, for ordered attributes).
538
-
Lower total scores rank higher.
539
-
This keeps Attribute before Proximity while preventing a record from being boosted just because a single word of a multi-word query matched in a high-ranked attribute.
540
-
Recommended with unordered attributes for any long-text field.
0 commit comments