Best field type for boosting all documents

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Best field type for boosting all documents

Ashwin Ramesh
Hi everybody,

We have a usecase where we want to push a popularity boost for each
document in our collection. When a user searches for any term, we would
like to arbitrarily add an additional boost by this value (which is
different for each document).

E.g. q=foo&boost=def(popularityBoostField,1)

Should we define the field 'popularityBoostField' as a docValue or regular
field?

If the field is sparsely filled, will that cause any issues?

Regards,

Ash

--
*P.S. We've launched a new blog to share the latest ideas and case studies
from our team. Check it out here: product.canva.com
<https://product.canva.com/>. ***
** <https://www.canva.com/>Empowering the
world to design
Also, we're hiring. Apply here!
<https://about.canva.com/careers/>
 <https://twitter.com/canva>
<https://facebook.com/canva> <https://au.linkedin.com/company/canva>
<https://twitter.com/canva>  <https://facebook.com/canva
<https://au.linkedin.com/company/canva>  <https://instagram.com/canva>






Reply | Threaded
Open this post in threaded view
|

Re: Best field type for boosting all documents

Paras Lehana
Hey Ashwin,

We, at Auto-Suggest, had the similar requirement. We wanted to boost
suggestions as per their demand. For this, we also introduced a new
*integer* field *demand*. We simply boosted it by (we use some mathematical
transformations so showing the basic version here):

*&boost=demand*


We use eDismax query parser. Since this is a numeric field, you get the
uninverted index (uninvertible = true) by default. Anyways, as the
recommendations in docValues section
<https://lucene.apache.org/solr/guide/8_1/docvalues.html#sorting-faceting-functions>
suggests
using docValues for fields on you expect to do faceting, sorting and
function queries, we enabled docValues for demand and tried the performance
gain in using boost for demand.
*Well, we didn't see any significant gains by enabling docValues on a
numeric field. *



On Mon, 16 Sep 2019 at 12:57, Ashwin Ramesh <[hidden email]> wrote:

> Hi everybody,
>
> We have a usecase where we want to push a popularity boost for each
> document in our collection. When a user searches for any term, we would
> like to arbitrarily add an additional boost by this value (which is
> different for each document).
>
> E.g. q=foo&boost=def(popularityBoostField,1)
>
> Should we define the field 'popularityBoostField' as a docValue or regular
> field?
>
> If the field is sparsely filled, will that cause any issues?
>
> Regards,
>
> Ash
>
> --
> *P.S. We've launched a new blog to share the latest ideas and case studies
> from our team. Check it out here: product.canva.com
> <https://product.canva.com/>. ***
> ** <https://www.canva.com/>Empowering the
> world to design
> Also, we're hiring. Apply here!
> <https://about.canva.com/careers/>
>  <https://twitter.com/canva>
> <https://facebook.com/canva> <https://au.linkedin.com/company/canva>
> <https://twitter.com/canva>  <https://facebook.com/canva>
> <https://au.linkedin.com/company/canva>  <https://instagram.com/canva>
>
>
>
>
>
>
>

--
--
Regards,

*Paras Lehana* [65871]
Software Programmer, Auto-Suggest,
IndiaMART Intermesh Ltd.

8th Floor, Tower A, Advant-Navis Business Park, Sector 142,
Noida, UP, IN - 201303

Mob.: +91-9560911996
Work: 01203916600 | Extn:  *8173*

--
IMPORTANT: 
NEVER share your IndiaMART OTP/ Password with anyone.