In Solr 7 document boosting aka index time boosting support has been dropped entirely.

This feature was used for the TypeBoost & HtmlFilter processors. In Search API Solr a similar feature has been implemented that gives the same result and uses lucene payloads.

When setting the boost to 0 for a bundle in the TypeBoost SearchApiProcessor the score for all documents of that bundle will be 0!

For example:

[details] => Array
                        (
                            [0] => Array
                                (
                                    [match] => 1
                                    [value] => 8.615736
                                    [description] => sum of:
                                    [details] => Array
                                        (
                                            [0] => Array(4)
                                        )

                                )

                            [1] => Array
                                (
                                    [match] => 1
                                    [value] => 0
                                    [description] => float(boost_document)=0.0
                                )

                        )

The boost factor for the entire document is 0. 8.615736*0=0

We should update the description in the UI to make this clear to the end user.

For HtmlFilter it now reads:
"Assign a boost of 0 to ignore the text content of that HTML element."

For TypeBoost there's no documentation yet, we could set this:
"Assign a boost of 0 to not score the item at all."

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mpp created an issue. See original summary.

mpp’s picture

Project: Search API Solr » Search API
Version: 8.x-3.x-dev » 8.x-1.x-dev
mpp’s picture

Assigned: mpp » Unassigned
Status: Active » Needs review
FileSize
681 bytes

Added a description:

           '#description' => $this->t('Assign a boost of 0 to not score the item at all.'),
mpp’s picture

Issue summary: View changes
FileSize
176.38 KB
mkalkbrenner’s picture

If the DB backend behaves the same way, we should add that description!
Thomas, would do you think about it?

drunken monkey’s picture

Yes, this makes a lot of sense. Thanks for the suggestion!
This does work the same in the DB backend, I think: results with item boost 0 will just always be ranked last when sorting by relevance.
Maybe we should also note that 1 is the default, though? Or would you say that’s clear enough?

borisson_’s picture

Status: Needs review » Reviewed & tested by the community

I think this is clear enough.

  • drunken monkey committed 9e05b94 on 8.x-1.x authored by mpp
    Issue #3054875 by mpp, drunken monkey, borisson_: Fixed help text for "...
drunken monkey’s picture

Status: Reviewed & tested by the community » Fixed

Alright, good to hear.
Committed. Thanks again, everyone!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.