Boost Scoring/Weighting

[msj121]

Describe your feature request

When searching to allow other factors, like recency or popularity to affect the weighting.

Re-ranking is not suitable - since it might only re-rank the page of 10, not "all" results. To prevent the database from querying every single element to adjust, perhaps a cosine/weight cut-off or a limit of results to be considered. Or a max on the adjustment could cut off what effect this weight adjustment would have.

However, the database would after this weight cut-off (or recognizing no adjustment could become a result), re rank with a boost from other properties, perhaps like so:

// Goal: views will boost the result, similar to a filter perhaps?
additionalFilter: {path[“views”],adjust:0.1,max:0.01};
// max(0.1,1000 views*0.1)+weight
or
additionalFilter: {path[“views”],adjust:0.1,max:0.01, method: “multiply”};
// max(0.01,1000 views*0.1) * weight
or
additionalFilter: {path[“views”],adjust:0.1, max:0.01,percentMax:10000};
// adjust here would be meaningless.
// max(0.01,1000 views/10000)*weight

I think multiple options should be made available to boost - but I am not sure all the possibilities, but even a few would be extremely useful.

Code of Conduct

• I have read and agree to the Weaviate's Contributor Guide and Code of Conduct